Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The mod_proxy configuration is not compatible with current AMS #1069

Open
rbotha78 opened this issue Apr 25, 2023 · 3 comments
Open

The mod_proxy configuration is not compatible with current AMS #1069

rbotha78 opened this issue Apr 25, 2023 · 3 comments

Comments

@rbotha78
Copy link
Member

The generated vhost files for author and publisher includes a block that's using a directive (SSLProxyEngine) not available in Apache 2.4.6 that's deployed on standard AMS.

AH00526: Syntax error on line 66 of /etc/httpd/conf.d/enabled_vhosts/aem_author.vhost:
Invalid command 'SSLProxyEngine', perhaps misspelled or defined by a module not included in the server configuration

This directive appears to only be available in Apache 2.4.30+

Furthermore, the proxy directory missing if the commerce module is not enabled, resulting in a startup failure.

httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 35 of /etc/httpd/conf.d/dispatcher_vhost.conf: Syntax error on line 67 of /etc/httpd/conf.d/enabled_vhosts/aem_author.vhost: Could not open config directory /etc/httpd/conf.d/proxy: No such file or directory

and if the directory is created, startup still fails due to the use of Include instead of IncludeOptional

httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 35 of /etc/httpd/conf.d/dispatcher_vhost.conf: Syntax error on line 67 of /etc/httpd/conf.d/enabled_vhosts/aem_author.vhost: No matches for the wildcard '*.proxy' in '/etc/httpd/conf.d/proxy', failing (use IncludeOptional if required)


@krystian-panek-wttech
Copy link

so probably only the type of the "include" will need to be changed as a quick win? :)

@EsteBustamante
Copy link

I don't know how ugly this could be, but we could work around with something like

<IfModule mod_proxy.c>
   <IfModule mod_ssl.c>
          SSLProxyEngine on
   </IfModule>
   IncludeOptional /etc/httpd/conf.d/proxy/*.proxy
</IfModule>

@krystian-panek-wttech
Copy link

sure @EsteBustamante but the key thing here to have it working after generating a project from archetype. not to be forced to do one extra step after ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants