[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: trying to grab a web page and write to IFS on iseries
Hi Thomas,
On 2/15/2012 2:23 AM, thomas.raddatz@xxxxxx wrote:
> As a side note, a complete list of redirection codes can be found here:
> [1]http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
> That list of status codes implies that is may not be save enough to
> rely on the 302 code, only. I decided for me to test for 301, 302, 303
> and 307 status codes because for me these codes seems to be the most
> reasonable ones.
301 should *not* redirect. It is a permanent change of address. When you
get a 301, you should notify the user to update his URL.
Technically, according to the standards, 302 wasn't supposed to
redirect, either... but every browser has used 302 as a redirect since
HTTP/1.0, so that behavior needs to be maintained, otherwise sites won't
work.
Every redirect I've ever seen coded in the "real world" (as opposed to
standards docs) uses a 302.
303 is the newer, standards-blessed, code to do what 302 has always done
in browsers. 302 and 303 work identically.
307 is a different code altogether. Unlike 302/302, where you always
use GET to access a redirected-to location, 307 keeps the same HTTP
method you started with. That's an interesting one! I've never seen
this done in a real application.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------