Ex: Re: Issue with Shibboleth SP - Endpoint Mismatch Error

[Paul B. Henson]

> From: Peter Schober
> Subject: Ex: Re: Issue with Shibboleth SP - Endpoint Mismatch Error
> 
> "https://... did not match http://"

Oooh, good catch; my eyes completely blurred over the missing s 8-/.

> I suppose that Jetty simply ignores these and simply determines the
> protocol by being access over plain http?

If you want jetty to process the X-Forwarded-* headers you need to enable the http-forwarded module and configure if necessary to match your environment.