-
Notifications
You must be signed in to change notification settings - Fork 2k
http-proxy does not support the Expected header: 100-continue #1219
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
Comments
The "proxyReq" callback is invoked too late to apply additional headers. |
Would it be possible to set request headers after the proxyReq event callback? Or perhaps detect whether |
As a workaround, I currently set all my headers on the incoming request object inside the HTTP server's "request" event callback. That way they get copied onto the outgoing proxied request before the |
This is my workaround, maybe it helps someone:
|
Anything new on this ? |
If I use http-proxy only as requester, there is a problem with 100-continue.
When we have a response from server with status 100 the requester in http-proxy (proxyReq in web-incoming) do not handle event "continue" and "socket hang up"
The text was updated successfully, but these errors were encountered: