Describe the bug
While running the sso-proxy (version 2.0.0) application in a Docker container with the environment variable SKIP_AUTH_PREFLIGHT set to "true", the OPTIONS preflight requests are receiving 301 status codes, which browsers such as Chrome and Firefox will interpret as a failed preflight check. I expected these to make it to my upstream resource and the response returned directly instead of receiving a 301 response.
To Reproduce
Steps to reproduce the behavior:
Run the sso-proxy Docker container with env var SKIP_AUTH_PREFLIGHT set to "true".
Construct a preflighted request (see below) to a separate domain protected by the same sso-proxy.
Expected behaviorOPTIONS preflight requests should be forwarded upstream when SKIP_AUTH_PREFLIGHT and should return the proxied response directly (instead of 301). (Note: I see in the tests an expected return value of http.StatusOK with skipAuthPreflight set to true).
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Describe the bug While running the sso-proxy (version 2.0.0) application in a Docker container with the environment variable
SKIP_AUTH_PREFLIGHT
set to"true"
, theOPTIONS
preflight requests are receiving 301 status codes, which browsers such as Chrome and Firefox will interpret as a failed preflight check. I expected these to make it to my upstream resource and the response returned directly instead of receiving a 301 response.To Reproduce Steps to reproduce the behavior:
SKIP_AUTH_PREFLIGHT
set to"true"
.Sample preflighted request:
Expected behavior
OPTIONS
preflight requests should be forwarded upstream whenSKIP_AUTH_PREFLIGHT
and should return the proxied response directly (instead of 301). (Note: I see in the tests an expected return value ofhttp.StatusOK
withskipAuthPreflight
set totrue
).Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):