On Thu, Sep 05, 2002 at 05:48:51PM +0200, Jacek Prucia wrote: > Yep. I was thinking about treating all subsequent request kinda like > separate URL list. Just like a stack. Flood gets 3xx response -- it > makes a new temporary urllist and copies current URL and location from > response to it, does switch and goes on. If it needs to repeat that (401 > or another 3xx) -- fine. When it hits 2xx type response it goes back to > url where fork has occured. Of course there are few issues to take care > about: time measure, detection of redirect loops and so on. Besides that > we have no way for farmer to switch urllist on the fly -- that would be > needed first. Does that makes sense?
Yeah, a stack is probably the right data structure to use here. I'm not sure if we should detect redirect loops or not. That gets pretty complicated to enforce (mainly because it *is* valid to see a URL twice in one profile). I'd guess I'd prefer it just sitting in an infinite loop rather than trying to test redirect loops unless we have a precise detection algorithm. -- justin
