-
Notifications
You must be signed in to change notification settings - Fork 57
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
Causes uncaught TypeError: object is not a function #42
Comments
I should note that I run into this behavior when using |
Can you show me a demo to reappear this problem? |
I will try to produce a self-contained repro. |
I'm getting a similar error, both version 2.2.0 and 3.1.1 when trying to use it with
The error doesn't occur when not using |
This may actually be a Node.js issue, as the default |
Same issue in this thread: chimurai/http-proxy-middleware#39 (comment) Hopefully you guys can help to solve it. Reproducible with a tiny example (created by @EladBezalel)
Here is some debug logging from the example:
|
https://blogs.msdn.microsoft.com/chiranth/2013/09/20/ntlm-want-to-know-how-it-works/ Looks like it fails somewhere between 2nd request and 2nd response. request headers [1]
response headers [1]
request headers [2]
response headers [2]
|
@chimurai Which node version? |
tested with v6.2.1 and v7.71 |
Found the issue in @ngbrown This might fix the issue you're having, since webpack-dev-server is using http-proxy-middleware to do the proxying. |
There is still an issue in Node proper, however, as I encounter this error using Node's own http.Agent in keepalive mode. |
I'm trying to use this in combination with the AWS SDK. After some number of requests, this uncaught error is thrown:
Using the default Node agent does not cause this behavior. This is on Node 4.5.0.
The text was updated successfully, but these errors were encountered: