-
Notifications
You must be signed in to change notification settings - Fork 32
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
Support for http.ClientRequest#setHeader, #getHeader, #removeHeader #5
Comments
@ChrisC : I've run into this issue when I was making sure sepia worked with the request library. The discussion you linked to hits the nail on the head. Indeed, the fundamental problem is that the "dummy" request sepia provides does not behave like an http.ClientRequest because it isn't one. I like the approach nock takes, and it would be great to have that in sepia. The implementation in nock isn't exactly self-contained, so it'll take some work to get a corresponding implementation in sepia. |
I just ran into this issue today. Did you find a workaround, @ChrisC ? |
I fixed the problem by switching to node-replay. |
Also ran into this while trying out sepia - attempting to use it with supertest. |
Bump |
Hi @ajsharp: I actually haven't committed to this:
What would be great is a minimal test case, and then I could probably just stub out the necessary methods. |
Running to problems when using with supertest as well. |
Am running into a lot of problems using Sepia with Superagent. I've determined that the problem is that methods such as setHeader, getHeader are removed from http.ClientRequest. See the issue and solution as described here for the Nock VCR lib :
nock/nock#41
jherdman/nock@0f4e634
Would it be inadvisable to add something similar to Sepia?
The text was updated successfully, but these errors were encountered: