We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
My config are like the following one:
(pathRewrite) { '^/api/one' : '', '^/api/two' : '' }
{ '^/api/one' : '', '^/api/two' : '' }
and
(proxyTable) { '/one' : 'http://localhost:3001', '/two' : 'http://localhost:3002' }
{ '/one' : 'http://localhost:3001', '/two' : 'http://localhost:3002' }
My use case is that I need the complete path to choose the correct proxy, and only after that it should apply my rules concerning pathRewrite.
If I put the pathRewrite step after the proxyTable one, it works well.
Have I missed something? What would be a solution?
The text was updated successfully, but these errors were encountered:
Ok, I should have looked more, looks like it is going to change in v0.10 :)
Sorry, something went wrong.
It's indeed going to change in v0.10.0. (fixed in PR #49)
v0.10.0
the beta is available via npm: npm install http-proxy-middleware@0.10.0-beta
npm install http-proxy-middleware@0.10.0-beta
Could you close the issue if it fixes the issue?
Thank you for your reactivity.
No branches or pull requests
Hi,
My config are like the following one:
(pathRewrite)
{ '^/api/one' : '', '^/api/two' : '' }
and
(proxyTable)
{ '/one' : 'http://localhost:3001', '/two' : 'http://localhost:3002' }
My use case is that I need the complete path to choose the correct proxy, and only after that it should apply my rules concerning pathRewrite.
If I put the pathRewrite step after the proxyTable one, it works well.
Have I missed something?
What would be a solution?
The text was updated successfully, but these errors were encountered: