- From: Roy T. Fielding <fielding@kiwi.ICS.UCI.EDU>
- Date: Thu, 10 Oct 1996 03:29:17 -0700
- To: Koen Holtman <koen@win.tue.nl>
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Clarification ...
> Many content authors have managed to avoid the confirmation dialog
> problem by using GETs for form submission instead of safe POSTs.
> However, this escape is not possible for forms
>
> a) which are (sometimes) used to submit large amounts of data
> b) which are (sometimes) used to submit data in a charset other
> than ISO-8859-1.
>
> Case b) will be the increasingly common; web internationalization [2]
> makes it necessary to use the POST method for form submission.
This is not true. The only time that web internationalization might
impact the choice of POST vs GET is when it is not known what the input
character set will be *and* it is possible for the user agent to submit
data in some character set other than what is expected *and* the form
does not contain an entry box for the user to select which particular
character set they are using *and* nobody has convinced the browser
community to include a standard hidden form field containing the charset
whenever the charset is not the same as that of the output form.
In other words, i18n has nothing to do with it.
...Roy T. Fielding
Department of Information & Computer Science (fielding@ics.uci.edu)
University of California, Irvine, CA 92697-3425 fax:+1(714)824-4056
http://www.ics.uci.edu/~fielding/
Received on Thursday, 10 October 1996 03:38:17 UTC