-
Notifications
You must be signed in to change notification settings - Fork 234
Issues: villadora/express-http-proxy
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
connection is reset when the request header Transfer encoding is set to chunked
#554
opened Dec 10, 2024 by
rohithkk
copyProxyResHeadersToUserRes overwrites Set-Cookie headers that have already been set by previous middleware
#547
opened Aug 16, 2024 by
fabb
Connection reset on "payload too large" (413) response from target server
#546
opened Aug 14, 2024 by
mdmower-csnw
content-length
request header is removed when parseReqBody
is false
#545
opened Aug 13, 2024 by
mdmower-csnw
Can I prevent express-http-proxy from unescaping string characters?
#496
opened Dec 14, 2021 by
ghost
"range" header is copied from container options even though it should be transitory
#494
opened Dec 8, 2021 by
davedx
form-urlencoded requests do not proxy correctly if content-type contains a semi-colon
closed in main line
#488
opened Oct 16, 2021 by
codefactor
proxyReqBodyDecorator value is not returned if parseReqBody == false
#484
opened Jun 3, 2021 by
jamonkko
Do not terminate request after proxy response. Add option to pass proxyResponse to next middleware
#477
opened Jan 7, 2021 by
hpl002
Cannot proxy requests to another service within docker-compose
#476
opened Jan 4, 2021 by
crisguitar
Setting Content-Type header in sendProxyRequest when parseReqBody throws exception
#472
opened Nov 19, 2020 by
gman-76
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.