Toerless Eckert <[email protected]> wrote: > I think multiple redirects can make a lot of sense, as Mcr said for > resale chains for example. I wouldn't be too bothered with DoS attacks > an attepting to come up with a tiny number. I'd rather go with a > number larger than what i can think of being useful. 10 for example. I > could build a load-sharing ring with that ("I am busy, try next") of > reasonable size.
I agree: a limit of 2-3 is silly. O(10) is correct.
O(100) is excessive.
> I my pet topic of course is diagnostics of non-malicious misconfigs.
> So, when a pledge is redirected from
> https://domain3.com/.well-known/brski/requestvoucher
> https://domain4.com/.well-known/brski/requestvoucher
> Could we make the pledge actually do the get with a breadcrump trail:
> On https://domain4.com connection: GET
>
/.well-known/brski/requestvoucher?brskiredirpath=domain3.com,domain2.com,domain.com
Doesn't the HTTP header Referrer include this kind of thing?
Or if not, is there another header?
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
