oauth2-proxy: 7.5.0 breaks protected path /static, HTTP 404
Expected Behaviour
Protected resource can still host on /static, just like in 7.4.0
Current Behaviour
404 page not found on resources hosted on /static Caused by https://github.com/oauth2-proxy/oauth2-proxy/pull/2025
Possible Solution
Rolling back to 7.4.0
Steps to Reproduce (for bugs)
Host a resource that has content on /static, for example jupyter login to the oauth proxy
the page does not fully load, requests to /static get a 404 response
calling the proxy on port 8080
kubectl debug -n tools -it jupyterlab-98c75c5c8-8qxq8 --image=curlimages/curl -- curl "http://localhost:8080/jupyter/static/lab/main.bcccfe17b7cd76ace990.js?v=bcccfe17b7cd76ace990"
Defaulting debug container name to debugger-rtpwv.
404 page not found
calling the underlying service on port 8888
kubectl debug -n tools -it jupyterlab-98c75c5c8-8qxq8 --image=curlimages/curl -- curl "http://localhost:8888/jupyter/static/lab/main.bcccfe17b7cd76ace990.js?v=bcccfe17b7cd76ace990"
Defaulting debug container name to debugger-rtpwv.
(()=>... (a valid response)
Context
Will roll back for now
Your Environment
containers:
- name: oauth2-proxy
image: quay.io/oauth2-proxy/oauth2-proxy:v7.5.0
ports:
- containerPort: 8080
args:
- "--upstream=http://localhost:8888"
- "--banner=-"
- "--footer=-"
- "--custom-sign-in-logo=-"
- "--cookie-secure=true"
- "--cookie-expire=8h0m"
- "--cookie-refresh=60m"
- "--cookie-domain=censored.de"
- "--http-address=0.0.0.0:8080"
- "--proxy-prefix=/jupyter"
- "--redirect-url=https://censored.de/jupyter/callback"
- "--email-domain=censored.de"
- "--provider=oidc"
- "--client-id=123456"
- "--oidc-issuer-url=https://login.microsoftonline.com/987645/v2.0"
- Version used: 7.5.0, 7.5.1
About this issue
- Original URL
- State: open
- Created 10 months ago
- Comments: 26 (6 by maintainers)
Commits related to this issue
- #2223 - Move static content to oauth2-proxy-static to avoid name collisions — committed to StefanLobbenmeierObjego/oauth2-proxy by deleted user 6 months ago
You are welcome 😃 Thank you for your effort!
@tuunit can you reopen the issue since we now also know the cause and fix?
Edit: thanks 😄