The presence of the x-forwarded-port is a pretty good clue that a proxy or load
balancer is in front of the app:
https://en.wikipedia.org/wiki/X-Forwarded-For
Yes, you should check the x-forwarded-port header first, and if it is 443,
ignore the rest.
Better still is to check the x-forwarded-pro
Chuck,
(as always to the rescue, you the man! Thanks!)
> On 7. 4. 2017, at 6:41 PM, Chuck Hill wrote:
> Is there a SSL terminating proxy or load balancer in front of the new
> installation?
Absolutely no idea :( Aside of asking the side admin, might I check somehow?
> x-forwarded-port is more
Is there a SSL terminating proxy or load balancer in front of the new
installation? x-forwarded-port is more standard and dependable in that case.
The other headers are from mod_webobjects.
Chuck
On 2017-04-07, 9:31 AM, "Webobjects-dev on behalf of OC"
wrote:
Hi there,
my a
Hi there,
my ages-old code to support SSL
- gets the request
- checks its server_port and x-webobjects-server-port headers
- if at least one of them is 443, we were accessed under SSL and all is well
and swell. Otherwise, it generates 302 and HTTPS URL to re-direct to the same
page under SSL.
