302 redirect for my get servlets on dispatcher to publish server. | Community
Skip to main content
Level 3
January 2, 2017
Solved

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

  • January 2, 2017
  • 2 replies
  • 2671 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Runal_Trivedi

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.

2 replies

Runal_Trivedi
Runal_TrivediAccepted solution
Level 6
January 2, 2017

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.

Level 3
January 2, 2017

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.