Retry-After response HTTP header indicates how long the user agent should wait before making a follow-up request. There are two main cases this header is used:
503(Service Unavailable) response, it indicates how long the service is expected to be unavailable.
301(Moved Permanently), it indicates the minimum time that the user agent is asked to wait before issuing the redirected request.
Retry-After: <http-date> Retry-After: <delay-seconds>
Dateheader for more details on the HTTP date format.
Support for the
Retry-After header on both clients and servers is still inconsistent. However, some crawlers and spiders, like the Googlebot, honor the
Retry-After header. It is useful to sent it along with a
503 (Service Unavailable) response, so that search engines will keep indexing your site when the downtime is over.
Retry-After: Wed, 21 Oct 2015 07:28:00 GMT Retry-After: 120
|RFC 7231, section 7.1.3: Retry-After||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
|Feature||Android||Chrome for Android||Edge mobile||Firefox for Android||IE mobile||Opera Android||iOS Safari|
1. See Bug 230260.
© 2005–2017 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.