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
We encountered an issue after updating Vividus from version 0.6.3 to 0.6.14.
The problem is related to the new header management in Vividus. Some GET API calls started returning the following error: "Bad chunk header: {%body of JSON response%}"
We found that this issue is connected to a stricter header policy enforced by some APIs.
Background
In our tests, we set up a few additional custom headers:
X-Request-Id
X-Mashery-Oauth-Client-Id
Authorization
Content-Type
X-Mashery-Oauth-Scope
X-Mashery-Oauth-User-Context
After adding these custom headers, Vividus automatically adds some "default" headers.
We encountered an issue after updating Vividus from version 0.6.3 to 0.6.14.
The problem is related to the new header management in Vividus. Some GET API calls started returning the following error:
"Bad chunk header: {%body of JSON response%}"
We found that this issue is connected to a stricter header policy enforced by some APIs.
Background
In our tests, we set up a few additional custom headers:
X-Request-Id
X-Mashery-Oauth-Client-Id
Authorization
Content-Type
X-Mashery-Oauth-Scope
X-Mashery-Oauth-User-Context
After adding these custom headers, Vividus automatically adds some "default" headers.
Vividus Default Headers Comparison
Old Versions (0.6.3 - 0.6.13):
New Version (0.6.14):
Issue Details
The issue occurs with the
Connection
header. In the latest version, Vividus sends this header twice (keep-alive
andUpgrade
), which causes conflicts.We replicated the issue using Postman, which confirmed this theory.
Suggestion
Could we introduce a feature to manage these cases and allow control over certain "default" headers?
Artifacts
**Execution environment **
Additional context
Link to StackOverflow with similar issue and same resolution
https://stackoverflow.com/questions/71615000/postman-error-parse-error-invalid-character-in-chunk-size
The text was updated successfully, but these errors were encountered: