You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario: I've deployed code server under a path under your domain, the path structure is suffixed for each user id. For example:
http://mydomain.com/vscode --> app served here
http://mydomain.com/vscode/user1 --> url for individual user
While trying to serve a react app, I've noticed that requests were stripping out the vscode/user1, hence not hitting the webpack server in the react app with the right path.
Suggestion: Allows a generic argument to be set while starting the server that will accept a regex to enrich the path forwarded by the absproxy , eg something like: --absproxy-prefix, if this variable is set, the pathProxy will make use of it and forward the request after enrichment.
Why do you want this feature?
To simplify the deployment structure and allow get rid of the intermediary proxy.
I believe this feature will also benefit other users that are constrained on deployment code server using a proxy domain, as the path approach is simpler and easy to navigate from a enterprise security perspective.
Are there any workarounds to get this functionality today?
Yes, uses one additional reverse proxy next to vs code server, however the UX isn't great.
Are you interested in submitting a PR for this?
Yes
The text was updated successfully, but these errors were encountered:
What is your suggestion?
Scenario: I've deployed code server under a path under your domain, the path structure is suffixed for each user id. For example:
While trying to serve a react app, I've noticed that requests were stripping out the
vscode/user1
, hence not hitting the webpack server in the react app with the right path.This is the intended behaviour of pathProxy.ts
Suggestion: Allows a generic argument to be set while starting the server that will accept a regex to enrich the path forwarded by the
absproxy
, eg something like:--absproxy-prefix
, if this variable is set, the pathProxy will make use of it and forward the request after enrichment.Why do you want this feature?
To simplify the deployment structure and allow get rid of the intermediary proxy.
I believe this feature will also benefit other users that are constrained on deployment code server using a proxy domain, as the path approach is simpler and easy to navigate from a enterprise security perspective.
Are there any workarounds to get this functionality today?
Yes, uses one additional reverse proxy next to vs code server, however the UX isn't great.
Are you interested in submitting a PR for this?
Yes
The text was updated successfully, but these errors were encountered: