Acs commons routing issue for page not found

Forum|Forum|1 year ago
February 16, 2025
3 replies
625 views

ACS Commons routing to a 500 page instead of a 400 for "Page Not Found."

Example: I have a page at /content/sample/en/home.html. If I try to access hometest.html on Publisher1, it redirects to a 500 error page. The weird part is that on other publish servers, it correctly redirects to a 400 error page. All four publishers have the same configuration.

I'm using AEM 6.5.18 and ACS 4.4.0.

Your inputs are appreciated!

Best answer by vijayselvas1

Thanks Guys for your response. I have tried the given inputs, but no luck. Finally, I cleared the ACS commons cache from jmx console and its started routing to the 404.

kautuk_sahni

Employee

@estebanbustamante @aanchal-sikka @narendragandhi @somen-sarkar @ayush-anand @kapil_rajoria @sady_rifat @nishanth_kr @madalavenkat7 Your input would really help! If you have time, please review this question and share your thoughts.

Kautuk Sahni

V

vijayselvas1AuthorAccepted solution

New Participant

Thanks Guys for your response. I have tried the given inputs, but no luck. Finally, I cleared the ACS commons cache from jmx console and its started routing to the 404.

chaudharynick

New Participant

Hi @vijayselvas1

Can you check the error logs and see if the request URL is exactly the same or different?
Also check if there are any WARN or ERROR logs?

kapil_rajoria

New Participant

Hi @vijayselvas1, did you check the error logs for publisher1 and the network tab in the inspect? Try to check, if any redirect is happening.

Also, you can try comparing the dispatcher config.
Please share the insights here.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded