-
Notifications
You must be signed in to change notification settings - Fork 62
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
test_replays_response_from_cassette fails because of X-Amzn-Trace-Id #184
Comments
This is because httpbin has moved hosting providers. It makes sense to me for us to either:
Either way, contributions will be necessary for this as I'm not able to spend a significant amount of time on this. |
jhatler
added a commit
to jhatler/betamax
that referenced
this issue
Dec 23, 2023
The httbin.org service returns a X-Amzn-Trace-Id header in its responses, which is different for each request. This causes the tests to fail. This clears the header before comparing responses. Refs: betamaxpy#184, betamaxpy#190 Signed-off-by: Jaremy Hatler <[email protected]>
This was referenced Dec 23, 2023
jhatler
added a commit
to jhatler/betamax
that referenced
this issue
Dec 23, 2023
The httbin.org service returns a X-Amzn-Trace-Id header in its responses, which is different for each request. This causes the tests to fail. This clears the header before comparing responses. Refs: betamaxpy#184, betamaxpy#190 Signed-off-by: Jaremy Hatler <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The test code already removes some headers which may differ between requests but the difference shown above is in r1.content and I don't know what the best way is to ignore
X-Amzn-Trace-Id
there.It seems as if httpbin.org uses Amazon's Elastic Load Balancing which adds a unique
X-Amzn-Trace-Id
header. That header is different for each request.The text was updated successfully, but these errors were encountered: