On Fri, Sep 06, 2002 at 12:25:43PM +0200, Jacek Prucia wrote: > I think it would be nice for flood to follow HTTP RFC, just to be 'HTTP > compilant client'. Apache HTTPD server follows HTTP RFC, and flood > schouldn't be threated as 'worse' kind of software, that doesn't have to > do that. So, how about making flood a little bit more HTTP RFC > compilant? :) > > OTOH I somehow agree with Aaron. I think flood autmatic behaviour > schould be an option. Something like 'mimic browser'. We could then use > dynamic urllists for other things (like fetching all img's and embed's > from response and so on)
I don't see where in the spec it says clients "MUST" automatically redirect to the URLs specified in a 302 response. OTOH, I do see where it says: If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued. So yeah, optional sounds good to me if you need it. I'm just of the opinion that we should do as little automatically as possible, so that the user can tweak every little piece that they want (and so we can later add new functionality within the flexible constraints of the pieces we set up now). -aaron
