-
Notifications
You must be signed in to change notification settings - Fork 859
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
Removes port from target #985
Comments
Can you share your server + proxy configuration? |
Seems to be only the logging; https://codesandbox.io/p/devbox/gracious-lamport-jfds4x If you visit the /api or /web path, you see it excludes the port in the logging |
@Netail Yeah, looks like it is just the logging. Initially I thought I had an issue with the proxy but that seems to be working as intended. |
It also automatically adds a trailing slash to the target which could trigger an infinite loop when the web server has a redirect to the non-trailing slash path |
Thanks for reporting and the reproduction. Trailing slash is added by the |
published fix for port issue in 3.0.1-beta.0 |
Will you make a ticket there or shall I? |
Feel free to create a ticket 👍 |
Mhm I doubt it will be picked up, they haven't updated that library for over 4 years now, same for all the security issues |
Checks
http-proxy-middleware
.Describe the bug (be clear and concise)
When a target with a port is given, it gets proxied to the domain without port.
E.g. when using http://127.0.0.1:3001 as a target, it will proxy to http://127.0.0.1
Step-by-step reproduction instructions
Expected behavior (be clear and concise)
Go to the correct port
How is http-proxy-middleware used in your project?
What http-proxy-middleware configuration are you using?
What OS/version and node/version are you seeing the problem?
Additional context (optional)
No response
The text was updated successfully, but these errors were encountered: