Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support for Retry-After header #37

Open
GoogleCodeExporter opened this issue Apr 7, 2015 · 2 comments
Open

Support for Retry-After header #37

GoogleCodeExporter opened this issue Apr 7, 2015 · 2 comments
Labels
auto-migrated Component-HTTP Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

External references, such as a standards document, or specification?

http://tools.ietf.org/html/rfc2616#section-14.37

Java environments (e.g. Java 6, Android 2.2, App Engine 1.3.7)?

All.

Please describe the feature requested.

Retry-After is used on a 503 (Service Unavailable) or 3xx (Redirection) 
response to indicate the number of seconds to wait or the HTTP-date for when to 
reissue the request.  The HTTP library shoud process that and automatically 
wait the specified amount of time and then reissue the request.  It could 
potentially be customized by the maximum amount of time allowed to wait.

Original issue reported on code.google.com by yan...@google.com on 7 Oct 2010 at 12:21
@GoogleCodeExporter
Copy link
Author

Original comment by yan...@google.com on 12 Nov 2010 at 1:48

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Original comment by yan...@google.com on 8 Jan 2011 at 6:29

  • Added labels: Component-HTTP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-HTTP Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter