Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.
SOLVED

302 redirect for my get servlets on dispatcher to publish server.

Avatar

Level 4

I have few GET servlets registered on path /bin/****. This works fine on publish instances. However, when the site is requested via dispatcher, I could see that there is a 302 redirect to the publish server.

This is on a dev environment with https enabled. Any thoughts on this.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Rewriting URL is not something that dispatcher controls, rewrite mainly happens because of rewrite module in apache and rules configured.

I would suggest you enable rewrite logs in apache to debug level and see why it is issuing a 302 redirect.

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Rewriting URL is not something that dispatcher controls, rewrite mainly happens because of rewrite module in apache and rules configured.

I would suggest you enable rewrite logs in apache to debug level and see why it is issuing a 302 redirect.

Avatar

Level 4

Runal.Trivedi wrote...

Rewriting URL is not something that dispatcher controls, rewrite mainly happens because of rewrite module in apache and rules configured.

I would suggest you enable rewrite logs in apache to debug level and see why it is issuing a 302 redirect.

 

There were some reverse proxy redirect rules which was the reason.