Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM Publish displaying "It works!" for every URL | Dispatcher handles the request correctly

Avatar

Level 6

Hi All,

 

My publish instance on the cloud is giving the below result for every URL - 

Response -  <html><body><h1>It works!</h1></body></html>

Rohan_Garg_0-1661772117521.png

The favicon as you see is correctly loaded but the rest of the result is not.

The page "It works!" is as far as I know Apache Webserver's response.

 

However, when hitting from dispatcher the page us rendering correctly!

The Author's URL with query string ?wcmmmode=disabled is also generating the full page content.

 

What could be the reason for publish's behavior ?

 

When hitting from dispatcher here are the logs for the same - 

Request URL - https://domainA.com/content/brandA/us/en/home.html?rohangarg=trueAgain123456?

 

1. HTTPD Access

cm-p57fgf-e459abv-aem-publish-abcjsfh-24fh4 - - 29/Aug/2022:10:38:44 +0000 "GET /content/brandA/us/en/home.html?rohangarg=trueAgain123456 HTTP/1.1" 302 240 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36"
cm-p57fgf-e459abv-aem-publish-abcjsfh-24fh4 - - 29/Aug/2022:10:38:45 +0000 "GET /home?rohangarg=trueAgain123456 HTTP/1.1" 200 11374 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36"

 

2. AEM Dispatcher 

[29/Aug/2022:10:38:45 +0000] [I] [cm-p57fgf-e459abv-aem-publish-abcjsfh-24fh4] "GET /content/brandA/us/en/home.html?rohangarg=trueAgain123456" -2ms [brandA-farm/-] [actionhit] dev.domainA.com

 

3. HTTPD Error

Mon Aug 29 10:38:45.410243 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] Changing Host header to: dev.domainA.com.
Mon Aug 29 10:38:45.410504 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] Found farm domainA-farm for dev.domainA.com
Mon Aug 29 10:38:45.410524 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] checking [/content/brandA/us/en/home.html]
Mon Aug 29 10:38:45.410532 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] Query string ignored: rohangarg=trueAgain123456
Mon Aug 29 10:38:45.410559 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] never flushed [/mnt/var/www/html/content/brandA/us/en/.stat] -> use cache [/mnt/var/www/html/content/brandA/us/en/home.html]
Mon Aug 29 10:38:45.410568 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] cache-action for [/content/brandA/us/en/home.html]: DELIVER
Mon Aug 29 10:38:45.410571 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] request declined
Mon Aug 29 10:38:45.410608 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] response.headers[Content-Type] = "text/html;charset=utf-8"
Mon Aug 29 10:38:45.410620 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] response.headers[X-Content-Type-Options] = "nosniff"
Mon Aug 29 10:38:45.410630 2022 [dispatcher:debug] [pid 232:tid 140430993890104] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] response.headers[Age] = "20531"
Mon Aug 29 10:38:45.592394 2022 [dispatcher:debug] [pid 233:tid 140430995872568] [cm-p57yyy-e45zzzz-aem-publish-7fb74f76b-24fh4] Changing Host header to: publish-p57yyy-e45zzzz.adobeaemcloud.com.

 

@arunpatidar , @Mohit_KBansal , @kautuk_sahni 

 

Thanks,

Rohan Garg

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hi All,

 

The publish domain https://publish-pyyyyyy-ezzzzzz.adobeaemcloud.com/ if not handled by default.vhost is handled by the catch-all vhost in dispatcher_vhost.conf which redirects the to index web page in apache.

 

In the cloud deployment build log, if we check the Build Image Log -

 

2022-08-30 18:01:18 (10.3 MB/s) - '/tmp/dispatcher/dispatcher-configuration.zip' saved [21906/21906]+ validate_configuration /tmp/dispatcher/dispatcher-configuration.zip
+ local zippedConfiguration=/tmp/dispatcher/dispatcher-configuration.zip
+ local unzippedConfiguration=/tmp/dispatcher/unzippedConfiguration
+ mkdir -v -p /tmp/dispatcher/unzippedConfiguration
created directory: '/tmp/dispatcher/unzippedConfiguration'
+ unzip -d /tmp/dispatcher/unzippedConfiguration /tmp/dispatcher/dispatcher-configuration.zip
Archive: /tmp/dispatcher/dispatcher-configuration.zip
creating: /tmp/dispatcher/unzippedConfiguration/conf.d/
creating: /tmp/dispatcher/unzippedConfiguration/conf.d/available_vhosts/
creating: /tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/

 

inflating: /tmp/dispatcher/unzippedConfiguration/conf.d/available_vhosts/default.vhost

 

inflating: /tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/available_farms/default.farm

inflating: /tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/default.farm -> ../available_farms/default.farm

 

/tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/default.farm -> ../available_farms/default.farm

 

As we see from above for some reason the dispatcher is not picking up the default.vhost in enabled farms even though its there (both symlinks and actual file place have been tried)

Hence the fix for it involved creating a new publish serverName vhost which was an exact replica of default.vhost, this solved the problem and rendered the publish URLs correctly.

 

View solution in original post

1 Reply

Avatar

Correct answer by
Level 6

Hi All,

 

The publish domain https://publish-pyyyyyy-ezzzzzz.adobeaemcloud.com/ if not handled by default.vhost is handled by the catch-all vhost in dispatcher_vhost.conf which redirects the to index web page in apache.

 

In the cloud deployment build log, if we check the Build Image Log -

 

2022-08-30 18:01:18 (10.3 MB/s) - '/tmp/dispatcher/dispatcher-configuration.zip' saved [21906/21906]+ validate_configuration /tmp/dispatcher/dispatcher-configuration.zip
+ local zippedConfiguration=/tmp/dispatcher/dispatcher-configuration.zip
+ local unzippedConfiguration=/tmp/dispatcher/unzippedConfiguration
+ mkdir -v -p /tmp/dispatcher/unzippedConfiguration
created directory: '/tmp/dispatcher/unzippedConfiguration'
+ unzip -d /tmp/dispatcher/unzippedConfiguration /tmp/dispatcher/dispatcher-configuration.zip
Archive: /tmp/dispatcher/dispatcher-configuration.zip
creating: /tmp/dispatcher/unzippedConfiguration/conf.d/
creating: /tmp/dispatcher/unzippedConfiguration/conf.d/available_vhosts/
creating: /tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/

 

inflating: /tmp/dispatcher/unzippedConfiguration/conf.d/available_vhosts/default.vhost

 

inflating: /tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/available_farms/default.farm

inflating: /tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/default.farm -> ../available_farms/default.farm

 

/tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/default.farm -> ../available_farms/default.farm

 

As we see from above for some reason the dispatcher is not picking up the default.vhost in enabled farms even though its there (both symlinks and actual file place have been tried)

Hence the fix for it involved creating a new publish serverName vhost which was an exact replica of default.vhost, this solved the problem and rendered the publish URLs correctly.