It was thus said that the Great Kevin Sangeelee once stated: > If your test is simulating a faulty server, It's not so much simulating a faulty server as it is simulating an infinite nymber of redirects. It could possibly be server A -> server B -> server C -> server D -> server E -> server A (repeat). > there's as much responsibility > on your code to give some indication of failure as there is on a client to > detect the condition. How? Given that a redirection loop can exist across servers. > I'd suggest something less than 11,430, were I to be asked. So would I. -spc
---
Previous in thread (8 of 12): 🗣️ Philip Linde (linde.philip (a) gmail.com)
Next in thread (10 of 12): 🗣️ Kevin Sangeelee (kevin (a) susa.net)