Susan Aurand wrote: > I know the POST Method the data is sent to STDIN, and GET > method the data is attached to the URL and > then submitted. When and why would you want to use the GET > method versus the POST method. Is is > because of firewalls? or what? I would appreciate any input on this > subject. Thank You. > Susan Evans
RFC 2616 <ftp://ftp.isi.edu/in-notes/rfc2616.txt>, section 9.1.1 "Safe Methods", says: Implementors should be aware that the software represents the user in their interactions over the Internet, and should be careful to allow the user to be aware of any actions they might take which may have an unexpected significance to themselves or others. In particular, the convention has been established that the GET and HEAD methods SHOULD NOT have the significance of taking an action other than retrieval. These methods ought to be considered "safe". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is made aware of the fact that a possibly unsafe action is being requested. Naturally, it is not possible to ensure that the server does not generate side-effects as a result of performing a GET request; in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the side-effects, so therefore cannot be held accountable for them. If GET doesn't have any side effects besides retrieving data, the requests can be cached, bookmarked, etc. Also, although the standard does not set an absolute limit on the size of a request URI, browsers and servers likely implement various limits. So you may need to use POST when the argument list is large. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
