Article:		When to Use Get?
Subject:		If true? You're kidding, right?
Date:		2002-04-27 16:37:00
From:		Jess Holle
The article states: "The most commonly cited example is restrictions on the length of URLs. The suggestion is that some misuses of GET and POST have been workarounds for these problems, enabling web applications to work as intended. If true..." There is no IF about this. These browser restrictions force requests that should be done via GETs (according to HTTP guidelines) to be done via POSTs with alarming frequency in any real web application (vs. pretty marketing/informational web sites). This is a major issue in that in many techical spaces, GETs are easily performed and POSTs require nasty workarounds.

Previous Message

Next Message

• If true? You're kidding, right?
  2002-04-28 20:27:34 Mark Baker [Reply]
  
  I haven't found this at all. Perhaps it's how you design your resources. In general I'd say that if you frequently find your URIs are long, you're probably not doing something as well as you could be.

  
  MB
  
  

  • If true? You're kidding, right?
    2002-05-02 15:07:12 Yevgeniy Kaganovich [Reply]
    
    Interesting... I have a client application that sends a serialized Query object to the server so that the server can return a result set. Seems to me like a side-effect free operation...

    
    Also, even for only dealing with strings, the Java implementation of URL Encoding is utterly broken for i18n, so you must hack around it, which makes it a lot more painful to use GET than POST. http://www.w3.org/International/O-URL-and-ident.html

    
    I think GET would be a lot more useful if it didn't depend on URL semantics.