IIS 7.0 - Application Request Routing (ARR)

Re: Bug in "Reverse rewrite host in response headers"

anilr — Thu, 04 Jun 2009 16:44:29 GMT

This is useful for cases where the application server may do redirects/cookies based on its internal address rather than the public address accessible to the client.

This flag is not enabled by default.

Re: Bug in "Reverse rewrite host in response headers"

Doggy8088 — Wed, 03 Jun 2009 01:15:00 GMT

Could you tell me the exact meaning and description of the "reverse rewrite host in response headers" option?

Also, this checkbox is "checked" by default. Is that a normal situation?

Re: Bug in "Reverse rewrite host in response headers"

anilr — Tue, 02 Jun 2009 23:11:41 GMT

You need to uncheck the "reverse rewrite host in response headers" checkbox - this is causing the host in the Location header of the 301 response to be rewritten to the original host.

Bug in "Reverse rewrite host in response headers"

Doggy8088 — Tue, 02 Jun 2009 13:03:46 GMT

I configured my ARR as a reverse proxy only. In the ARR, the "Reverse rewrite host in response headers" checkbox is checked.

My internal website url is: http://internal.example.com/test.aspx

My external website url is: http://external.example.com/test.aspx

When I clicked http://internal.example.com/test.aspx, this page response a HTTP 301 Redirection to http://some.other.domain.com/testpage.aspx

When I clicked http://external.example.com/test.aspx link outside my office, it response a HTTP 301 but Redirect to http://external.example.com/testpage.aspx

I think this is a bug. The correct response Location should be "http://some.other.domain.com/testpage.aspx"

Does anyone can check it out?