-
Notifications
You must be signed in to change notification settings - Fork 5.9k
[V2] Documentation - Breaking change for Reverse proxy #1089
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Duplicate of #997 |
@sr229 just an FYI, I'm not sure it's a direct duplicate. I'm actually getting 404 responses from my reverse proxy.
Instead I get a 404 with my reverse-proxy 404 page. If code-server was erroring out on the server it would be a 5** error.
as well as
Which makes sense because what was returned was my reverse proxy 404 html page |
This was my fault; I accidentally excluded the webview HTML from the final build. It should be fixed in the latest v2 Docker image. |
@code-asher confirmed! Thank you for all of the awesome work!! |
code-server
version: v10.15.1Description
I have a similar issue to #997 after upgrading to V2, but it's different enough to warrent a separate issue.
I'm getting a 404, not found after upgrade for all web views (extension readme's, markdown preview etc.). But I don't think it's code-server's fault it's my reverse proxy config. I'm not sure the exact changes, but I think because I have some path matchers on my reverse proxy it's rejecting
/webview
paths as not found. because something obviously changed between v1 and v2, it should probably be documented.The text was updated successfully, but these errors were encountered: