[zope2-tracker] [Bug 1246591] Re: virtualhostmonster mappings doesn't handle https

Dylan Jay 1246591 at bugs.launchpad.net
Tue Aug 26 11:49:25 CEST 2014

We think the solution to this is to change VHM to look at HTTP_X_FORWARDED_PROTO, HTTP_X_FORWARDED_PORT and HTTP_X_FORWARDED_HOST headers. If these are present it will use these instead of the host header. 
- might need to make this optional behaviour. Is it a security risk if zope obeys these headers and there is no proxy in front? If we make it optional, would it be optional based on source IP?
- If VIRTUALHOSTBASE etc is present then we ignore these headers

We really need this so will create a pull request but we'd like feedback
someone disagrees with the plan.

You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

  virtualhostmonster mappings doesn't handle https

To manage notifications about this bug go to:

More information about the zope2-tracker mailing list