Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

403 Error

Avatar

Level 4

Hi Team,

 

When i access http://www.myserver.com/etc/segmentation/ or http://www.myserver.com/etc/clientcontext/default/ am getting an 403 error. Why am getting 403 error and why not 404??

Please help.

Thanks,

Madhu

1 Accepted Solution

Avatar

Correct answer by
Level 10

Webserver is protection layer for AEM. General recommendation is you should handle at webserver level apache with mod_rewrite to send 404.

View solution in original post

6 Replies

Avatar

Former Community Member

/etc/clientcontext/default/ and /etc/segmentation/ existing nodes and since they exist in repository it's a 403 error.

Avatar

Correct answer by
Level 10

Webserver is protection layer for AEM. General recommendation is you should handle at webserver level apache with mod_rewrite to send 404.

Avatar

Level 10

You get 404 if the URL is not resolved but here those URLs will be there but will not have access to load and hence would be getting 403

Avatar

Level 4

But why am getting forbidden?????

Avatar

Level 10

You should access through /miscadmin

this is the right URL to access segmentation

http://<host>:<port>/miscadmin#/etc/segmentation

Avatar

Level 4

Thank you so much for your reply.

But the isssue "we have been seeing the URLs appearing in Webmaster Tools as 403 errors. It's correct for them to get the 403 message, but crawlers shouldn't be able to see them at all."

How to handle this??

Your insights will be appreciated.

Thanks,

Madhu