If your test is simulating a faulty server, there's as much responsibility on your code to give some indication of failure as there is on a client to detect the condition. I'd suggest something less than 11,430, were I to be asked. Kevin Sent from phone On Tue, 27 Oct 2020, 02:16 Sean Conner, <sean at conman.org> wrote: > It was thus said that the Great John Cowan once stated: > > It seems to me that the limit on redirection should be purely a client > > issue rather than a hardwired part of the spec. Some clients won't want > to > > redirect at all, others will want to retry 1 or 5 or 100 times, depending > > on what they are being used for. > > The original limit was 5. But 9,015 (at the precise moment) is a bit > excessive. The limit of 5 was to help prevent the creation URL shortners > that are so prevelant on the web. > > Ah, I see that the limit is now mentioned in the Best Practices document, > not the specification. Still, a clent *should* give up redirections past > some amount (11,329 as of now). > > -spc (11430 ... ) > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201027/3066 bbdd/attachment.htm>
---
Previous in thread (4 of 12): 🗣️ John Cowan (cowan (a) ccil.org)
Next in thread (6 of 12): 🗣️ Philip Linde (linde.philip (a) gmail.com)