You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
Is there a way we can more loosely define he header matching? In one environment everything is fine, but in another I am seeing errors like: Invalid response header Content-Type: expected "application/json; charset=utf-8" but received "application/json;charset=utf-8" Invalid response header Vary: expected "Origin" but received "Origin, Accept-Encoding"
Is there a way to make this less strict, or do I just have to remove the expectation?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a way we can more loosely define he header matching? In one environment everything is fine, but in another I am seeing errors like:
Invalid response header Content-Type: expected "application/json; charset=utf-8" but received "application/json;charset=utf-8"
Invalid response header Vary: expected "Origin" but received "Origin, Accept-Encoding"
Is there a way to make this less strict, or do I just have to remove the expectation?
The text was updated successfully, but these errors were encountered: