On Fri, 15 Jun 2007, Marlon Bailey wrote:
I looked into how mod_proxy is handling this. They pass a
X-Forwarded-Port header value with the port of the client. So you can
rebuild the client information with
X-Forwarded-For
and X-Forwarded-Port
to tell whether the request was standard(port 80) or ssl(port 443) i
believe this would be a more general approach and seems to be working
for mod_proxy. But it's beyond the scope of my RFC.
This is not really ideal. Again, in a dev situation, you might be
listening on non-standard ports. Only the frontend server _really_ knows
if the connection used SSL or not, so it should report this directly to
the backend.
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/
_______________________________________________
List: Catalyst@lists.rawmode.org
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/
Dev site: http://dev.catalyst.perl.org/
