Sure--those are totally reasonable in most cases. However, the OP just said that all that's in the form is a single button, meaning most of those won't be an issue in this case.
-Jeff On May 15, 10:03 am, Tim Chase <[email protected]> wrote: > > If the form is just a single button, why not use GET and not have to > > deal with POST at all? > > Multiple reasons: > > * By spec, GET can be cached by intermediary proxies, POST > results aren't. Caching may change application behavior. (Yes, > there are workarounds that involve HTTP cache-control headers) > > * GET shouldn't perform any write-action on the server, while > POST can > > * POST can transmit large volumes of data (textareas and files in > particular) which can't be sent via GET which has size limits > (depends on both browser and server but 2kb is a good rule of > thumb for "too big", as I believe that's the limit imposed by IE > for the entire URL length) > > * GET requests often get saved in URL histories, leaving things > like passwords open to prying eyes > > Those are my first-pass list of reasons (there may be more) that > POST->GET translation isn't usually a good idea. > > -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
