Skip to content

CURLINFO_RETRY_AFTER: parse the Retry-After header value and offer it#4195

Closed
bagder wants to merge 4 commits into
masterfrom
bagder/retry-after
Closed

CURLINFO_RETRY_AFTER: parse the Retry-After header value and offer it#4195
bagder wants to merge 4 commits into
masterfrom
bagder/retry-after

Conversation

@bagder
Copy link
Copy Markdown
Member

@bagder bagder commented Aug 6, 2019

This patch series now contain the libcurl API change and it makes curl use it.

Ref: #3794

@bagder bagder changed the title CURLINFO_RETRY_AFTER: parse the Retry-Header value and offer it CURLINFO_RETRY_AFTER: parse the Retry-After header value and offer it Aug 6, 2019
@bagder bagder force-pushed the bagder/retry-after branch 2 times, most recently from c3123e8 to 8bf8f0b Compare August 6, 2019 12:04
bagder added 3 commits August 6, 2019 22:48
This is only the libcurl part that provides the information. There's no
user of the parsed value. This change includes three new tests for the
parser.

Ref: #3794
... instead of CURLINFO_EFFECTIVE_URL to avoid string operations.
If a Retry-After: header was used in the response, that value overrides
other retry timing options.

Closes #3794
@bagder bagder force-pushed the bagder/retry-after branch from 8bf8f0b to 9564c2d Compare August 6, 2019 20:48
@bagder bagder closed this in 640b973 Aug 7, 2019
@bagder bagder deleted the bagder/retry-after branch August 7, 2019 13:05
stain added a commit to stain/curl that referenced this pull request Oct 4, 2019
This completes curl#3794

Also make sure the new tests from curl#4195 are enabled
bagder pushed a commit that referenced this pull request Oct 5, 2019
This completes #3794.

Also make sure the new tests from #4195 are enabled

Closes #4465
@lock lock Bot locked as resolved and limited conversation to collaborators Nov 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Development

Successfully merging this pull request may close these issues.

1 participant