On May 17, 2007, at 6:56 PM, Dylan Vanderhoof wrote:
I'm having a little issue with SSL and uri_for.
mox_proxy is sending the X-Forwarded-For: headers correctly, but they
don't appear to have any information as to whether or not the request
was http or https. From what I can tell, this is normal behavior.
However, that means that if I'm just using http on the connection from
the proxy to the backend server, uri_for is incorrect, which causes
all
sorts of mixed-mode warnings to pop up on any subsequent requests.
using_frontend_proxy is set to 1 in my config, but it doesn't
appear to
address this particular issue.
Anybody have any suggestions for how I might fix this? For now, I'm
just running SSL to the backend server, but I'd really rather not
waste
the resources.
One way to solve this is to proxy SSL requests to a different port on
the backend, and set the environment variable HTTPS to 'ON' for that
port's virtualhost on the backend. Then Catalyst will know it's in
SSL mode and generate the right links.
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
