fix chunked client async_normal.hpp #248
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If response has ...<chunk>CLRF<hex>CLRF<data>... We need to skip past chunk-data ending CLRF, otherwise we find it again and on next iteration begin==iter
| @@ -452,7 +452,7 @@ | |||
| break; | |||
| if (len <= body_string.end() - iter) { | |||
| body.insert(body.end(), iter, iter + len); | |||
| std::advance(iter, len); | |||
| std::advance(iter, len+2); | |||
There was a problem hiding this comment.
Is it safe to do so if iter + len + 1 > body_string.end()? Haven't tested it, but probably instead of patching iterator here, line 450 should be:
std::advance(iter, distance(crlf.begin(), crlf.end()));
glynos
added a commit
that referenced
this pull request
Jun 12, 2013
fix chunked client async_normal.hpp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Chunked response for clients.
If response has
...CLRFCLRF...
We need to skip past chunk-data ending CLRF, otherwise we find it again and on next iteration begin==iter
It might not be the right fix for all cases, but it works for a local case with no chunk-extensions between chunk blocks.