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

[Dylan Jay]

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. 
Also
- 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.
https://bugs.launchpad.net/bugs/1246591

Title:
  virtualhostmonster mappings doesn't handle https

To manage notifications about this bug go to:
https://bugs.launchpad.net/zope2/+bug/1246591/+subscriptions