Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

Reset previous response headers before curl_exec #130

Merged
merged 1 commit into from
Oct 13, 2017

Conversation

mlocati
Copy link
Contributor

@mlocati mlocati commented Aug 25, 2017

Using the same client instance, if you perform a normal request and then a request using an output stream, the headers of the first request will be kept, resulting in two set of headers in the second call.

This causes all sort of errors, for instance

Too much content was extracted from the stream (X instead of Y bytes)

Using the same client instance, if you perform a normal request and then a
request using an output stream, the headers of the first request will be kept,
resulting in two set of headers in the second call.

This causes all sort of errors, for instance
Too much content was extracted from the stream (X instead of Y bytes)
@Xerkus Xerkus added the bug label Oct 13, 2017
@Xerkus Xerkus added this to the 2.7.0 milestone Oct 13, 2017
@Xerkus Xerkus merged commit be74593 into zendframework:master Oct 13, 2017
Xerkus added a commit that referenced this pull request Oct 13, 2017
Xerkus added a commit that referenced this pull request Oct 13, 2017
Xerkus added a commit that referenced this pull request Oct 13, 2017
@mlocati mlocati deleted the patch-1 branch October 13, 2017 11:31
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants