On 29/10/2007, Selvig, Andy <[EMAIL PROTECTED]> wrote:
> I agree, though, it would help to see the headers. What's the easiest
> way to examine the headers as they're being processed by Apache?
http://wiki.apache.org/httpd/WatchingHttpHeaders
--
noodl
---
riginal Message-
From: Vincent Bray [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 12:52 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] ProxyPassReverse Incorrectly Handling
Redirects
Your initial question was how to get mod_proxy_html to deal with
relative urls in Location
Your initial question was how to get mod_proxy_html to deal with
relative urls in Location: headers, right? I still maintain that it
*probably* can't, given its author's propensity to follow the spec. In
any case, it would help to see some examples of working and otherwise
headers.
I blame niq :)
29, 2007 11:32 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] ProxyPassReverse Incorrectly Handling
Redirects
On 29/10/2007, Selvig, Andy <[EMAIL PROTECTED]> wrote:
> The problem comes in when the application sends redirects to relative
> pages. If the application redirect
On 29/10/2007, Selvig, Andy <[EMAIL PROTECTED]> wrote:
> The problem comes in when the application sends redirects to relative
> pages. If the application redirects to /main/list, my browser goes to
> this page:
That's perhaps because the Location: header of redirects must always
be a full url. If
