diff options
| author | Michael Brown | 2014-03-07 18:19:36 +0100 |
|---|---|---|
| committer | Michael Brown | 2014-03-07 18:32:26 +0100 |
| commit | 42bf3b9aa949f5b53eeb164a4a405822a7038a0e (patch) | |
| tree | 252788d68ddc8b679ea3739f4fcf8ab50855854a /src/include | |
| parent | [http] Use a retry timer to trigger retried requests (diff) | |
| download | ipxe-42bf3b9aa949f5b53eeb164a4a405822a7038a0e.tar.gz ipxe-42bf3b9aa949f5b53eeb164a4a405822a7038a0e.tar.xz ipxe-42bf3b9aa949f5b53eeb164a4a405822a7038a0e.zip | |
[http] Automatically retry request on a 503 Service Unavailable
A web server may return a 503 Service Unavailable response along with
a Retry-After header to direct the client to retry the request at a
later time.
The Retry-After header may be a number of seconds, or a full HTTP
timestamp (e.g. "Fri, 7 Mar 2014 17:22:14 GMT"). We have no
reasonable way of parsing a full HTTP timestamp; if the server chooses
to use this format then we simply retry after a fixed 5-second delay.
As per RFC 2616, in the absence of a Retry-After header we treat a
status code of 503 Service Unavailable as being equivalent to 500
Internal Server Error, and immediately fail the request.
Requested-by: Suresh Sundriyal <ssundriy@vmware.com>
Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/include')
0 files changed, 0 insertions, 0 deletions