Description Dean Roberts 2001-10-10 22:49:47 EDT

When an HTTP client receives a status response in the range 300 - 399 (inclusive)
    it always attempts to redirect the request (as long as the number of redirects are within
    the allowed range).

    However, this conflicts with the HTTP spec (RFC2616) and causes problems with certain
    server applications (such as source forge).

   Specifically the specification states in section 10.3:

		The action required MAY be carried out by the user agent without interaction
	    with the user if and only if the method used in the second request is
	    GET or HEAD. 

   There is also a specific note for 303 that a POST is redirected as a GET request to
   facilititate login screens.  There is another interesting note that 302 responses are
  erroneously treatede as 303 responses by allmost all existing HTTP clients and that
  servers may rely on this erroneous behavoiur.  (This is the case with SourceForge which
  responds to a Login POST with a 302 and expects the client to do a redirected GET at the
  provided address.