-
Notifications
You must be signed in to change notification settings - Fork 87
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
HTTP status codes not recorded when not 200. #74
Comments
loudmouth
changed the title
HTTP status codes not recorded
HTTP status codes not recorded when not 200.
Oct 17, 2017
sethhoward
pushed a commit
to sethhoward/DVR
that referenced
this issue
Oct 31, 2017
This was referenced Oct 31, 2017
Closed
dmiluski
added a commit
that referenced
this issue
Feb 14, 2018
…ed-74 Fixes HTTP status codes not recorded when not 200. #74
It appears status codes are not recorded at all anymore. Also, HTTP headers are now absent for HTTP errors (previously they were present) |
This was referenced Jun 12, 2018
olegdanu-newstore
pushed a commit
to NewStore/DVR
that referenced
this issue
Sep 27, 2018
olegdanu-newstore
pushed a commit
to NewStore/DVR
that referenced
this issue
Sep 28, 2018
olegdanu-newstore
pushed a commit
to NewStore/DVR
that referenced
this issue
Sep 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My type used for storing errors returned by my API hold the http status code so that user's can get more information while debugging their failed requests. However, when writing acceptance tests that the correct status codes are returned, DVR simply returns HTTP status code 0 always.
It looks like the status code is not being recorded in the cassette.
Any chance we can also record the status code?
The text was updated successfully, but these errors were encountered: