AEM 6.2 Dispatcher Unresolved Issue

[phall_hershey]

Hello,

My organization is currently upgrading our AEM environment from 6.1 to 6.2.  We completed our stage setup and are experiencing zero issues.  The URLs are working without any issues.  However, when we move the same dispatcher code to PROD when we try testing the production URLs by spoofing our web browsers, each website produces a Not Found - The requested URL /en_us/home.html was not found on this server. 

On production, we don't receive any errors in the dispatcher.  When we go to https://www.sitedomain.com/content/site/en_us/home.html the page renders correctly without any issues.  However, when we remove /content/site, I get a Not Found error message.

Has anyone every experienced this issue before?  If so, how did you resolve the issue?  If not, do you have suggestions on how to get to the root cause?

Again, our stage environment is working perfectly fine with the code deployed in production.

Thanks in advance to anyone who helps!!

[Albin_Issac]

This is a known issue with 6.2 after upgrade, https URL's are not working

Refer - https://www.albinsblog.com/2017/04/in-place-upgrade-of-aem-to-62-version.html  (Https URL resulting with Page Not Found)

Regards

Albin I

[kautuk_sahni]

Please have a look at this thread:- Not Found The requested URL / was not found on this server.

Jörg Hoh​ Need you help in this Dispatcher issue!!

[phall_hershey]

Here is the Not Found error:

The requested URL /en_us/home.html was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

[phall_hershey · Accepted solution]

Thanks this was just what I was looking for.  The solution to my problem was found at the bottom of the page (link below).

Https URL' resulting with 404 after in place upgrade of 6.2(6.1 to 6.2)

In the dispatcher.any/clientheaders.any added "X-Forwarded-Port"

[Jörg_Hoh]

Hi,

the dispatcher sample config has switched to allow all headers (using the "*" wildcard); using it would have prevented your problem from appearing :-)

Jörg