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>tags/v1.20.1
|
|
||
43 |
|
43 |
|
44 |
|
44 |
|
45 |
|
45 |
|
|
46 |
|
|
46 |
|
47 |
|
47 |
|
48 |
|
48 |
|
49 |
|
|
|
||
88 |
|
89 |
|
89 |
|
90 |
|
90 |
|
91 |
|
|
92 |
|
|
|
93 |
|
|
|
94 |
|
|
91 |
|
95 |
|
92 |
|
96 |
|
93 |
|
97 |
|
|
|
||
185 |
|
189 |
|
186 |
|
190 |
|
187 |
|
191 |
|
|
192 |
|
|
|
193 |
|
|
188 |
|
194 |
|
189 |
|
195 |
|
190 |
|
196 |
|
|
|
||
342 |
|
348 |
|
343 |
|
349 |
|
344 |
|
350 |
|
345 |
|
|
|
|
351 |
|
|
|
352 |
|
|
346 |
|
353 |
|
347 |
|
354 |
|
348 |
|
355 |
|
|
|
||
664 |
|
671 |
|
665 |
|
672 |
|
666 |
|
673 |
|
|
674 |
|
|
|
675 |
|
|
|
676 |
|
|
|
677 |
|
|
|
678 |
|
|
|
679 |
|
|
|
680 |
|
|
|
681 |
|
|
|
682 |
|
|
|
683 |
|
|
|
684 |
|
|
|
685 |
|
|
|
686 |
|
|
|
687 |
|
|
|
688 |
|
|
|
689 |
|
|
|
690 |
|
|
|
691 |
|
|
|
692 |
|
|
|
693 |
|
|
|
694 |
|
|
|
695 |
|
|
|
696 |
|
|
|
697 |
|
|
|
698 |
|
|
|
699 |
|
|
|
700 |
|
|
|
701 |
|
|
|
702 |
|
|
|
703 |
|
|
|
704 |
|
|
|
705 |
|
|
|
706 |
|
|
667 |
|
707 |
|
668 |
|
708 |
|
669 |
|
709 |
|
|
|
||
701 |
|
741 |
|
702 |
|
742 |
|
703 |
|
743 |
|
|
744 |
|
|
|
745 |
|
|
|
746 |
|
|
|
747 |
|
|
704 |
|
748 |
|
705 |
|
749 |
|
706 |
|
750 |
|