Vincent- Thanks for the reply. Although the example I gave was a Rails app (in this case, running on Mongrel), I seem to get the same behavior with a Trac app I'm hosting as well.
Up to now I've been avoiding looking at a rails-specific solution because I'm hosting other applications (like Trac) as well as off the shelf rails (Instiki). It seems like doing this through Apache is more elegant than trying to hack up every application I'm running individually. Andy Selvig -----Original Message----- From: Vincent Bray [mailto:[EMAIL PROTECTED] Sent: Monday, October 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 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 you're using restful routes in rails, try _url rather than _path. Better still, figure out how to tell rails that it's routed at /wtbasement/ rather than /. I've a suspicion that it's possible but dependant on how rails is hosted (rails/fastcgi/etc). That'd remove the need for mod_proxy_html altogether. Perhaps you could fiddle routes.rb to fit? -- noodl --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
