On 05/11/2011 02:03 PM, Ben Niven-Jenkins wrote:
There's nothing to prevent HTTP 503 responses containing a Location:
header.
I haven't tested it but I'd be surprised if browsers (or in fact
many other clients) followed it in practice.
Yes, I agree. More so given that there is difference among browsers in
interpreting 301/302 uniformly.
IMO causing sawtooth behaviour as a result of using Retry-After is
because the server has a naive implementation. Sensible use of
Retry-After would allow a server to pace requests from clients
provided the clients honoured the heading.
In the end, no matter how you use R-A header, the result is the
same: the server utilization oscillates between busy load and
no load. For the period when the server has no load but it has
been quarantined based on the R-A header, it becomes useless and
contributes no goodput to the HTTP farm.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / [email protected]
Web: http://ect.bell-labs.com/who/vkg/
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
