I am pretty sure there is a simple solution for this issue and I am hoping someone can save me digging through piles of documentation.
We have a load balancer that sits in front of the web farm which terminates SSL. Between the SSL termination and the web site in the farm is HTTP traffic.
I can see that X-Forwarded-Proto, X-Forwarded-Host come through correctly to the sites and umbraco itself seems to recognise these headers.
OWIN does not. It recognises the host but not port header and as a result the redirection fails because its HTTP instead of HTTPS.
Google Auth (OWIN) - host name failure
Hi
I am pretty sure there is a simple solution for this issue and I am hoping someone can save me digging through piles of documentation.
We have a load balancer that sits in front of the web farm which terminates SSL. Between the SSL termination and the web site in the farm is HTTP traffic.
I can see that X-Forwarded-Proto, X-Forwarded-Host come through correctly to the sites and umbraco itself seems to recognise these headers.
OWIN does not. It recognises the host but not port header and as a result the redirection fails because its HTTP instead of HTTPS.
http://www.example.com instead of https://www.example.com which works for OAUTH with google.
Is there a quick setting here or do I need to intercept an event to allow the code to understand the X-Forwarded-Proto header?
is working on a reply...