On Aug 20, 7:17 am, elygre <[EMAIL PROTECTED]> wrote: > One consideration for using POST is that character set handling for > URLs is not always well defined, whereas the character set handling > for the post data is. For example, if I want to send stuff like Æ, Ø > or Å (norwegianl characters) on a URL, some servers expect ISO 8859, > whereas others expect UTF 8. Excellent point. I guess there is a natural tendency to view GET having tranparency, i.e, even a human can type the command. Where with post, it is more for sending data the human is not expected to type. I am not keen to the forcing of the POST only because normally, especially in AJAX related functionality, the input is light weight and straight forward. IOWs. there is more server overhead in processing a POST for small input conditions. IMV, the only "reasonable" and "practical" reason to forcing a POST is to reduce the population of exploring, curious minds. If the server required a POST for AJAX, then this effectively stops non-hackers from typing a request in the address bar. --- HLS
