-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fallback proxy doesn't work on Node v17+ #814
Comments
Having a similar problem, but even trying node v16.14.2 doesnt solve it for me. http-server 14.1.1 (latest) (Using TLS because browser requires it for Brotli support, but happens in http too.)
|
PSA: I ended up using sirv-cli with the |
Running into the same problem with |
http-server --proxy catch all does not seem to work with node 18 see http-party/http-server#814
As a workaround you can try using
or you can try
Messages from http-server output says:
meaning that |
This set of options finally worked for me while using Node 18: http-server ./build -a localhost -P http://localhost:3002? -p 3002
Available on:
http://localhost:3002
Unhandled requests will be served from: http://localhost:3002? |
I am using
But this doesn't:
It seems that there is an issue with the |
Environment Versions
16.14.2
&17.9.0
&18.0.0
&18.2.0
14.1.0
Steps to reproduce
http-server --proxy http://localhost:8080?
doesn't redirect deep paths to the root.I use NVM. When I switch to node.js
v16.14.2
everything works well. But not onv17.9.0
,v18.0.0
andv18.2.0
.Expected result
Actual result
The text was updated successfully, but these errors were encountered: