-
Notifications
You must be signed in to change notification settings - Fork 45
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
Content-Type header expects duplicate values #302
Comments
👋 Hi! The 'smartbear-supported' label has just been added to this issue, which will create an internal tracking ticket in PactFlow's Jira (PACT-1220). We will use this to prioritise and assign a team member to this task. All activity will be public on this ticket. For now, sit tight and we'll update this ticket once we have more information on the next steps. |
Yes also seen this Should be actually be warning the user on the consumer side that they have duplicate values in the content-type header. I think it stems from setting a request header with content type and a body in which you need to set the content_type header, it states that it should use the content_type header if set. Is there ever a case for a multi-value content-type header that has the same value as both indexes? or would you expect to have something else like a variant application/json+problem; |
It's a bug, in that prior to this version the behaviour was different. Any implementation that allows a user to specify the |
Rather than repeat the repro/details, this is an upstream issue to track pact-foundation/pact-js#1106.
The text was updated successfully, but these errors were encountered: