This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
That is false. The HTTP standard does not enforce a GET limitation. The limitation is a browser-dependent limitation. Meaning some browsers allow longer URL's than others.
RFC 2616 (Hypertext Transfer Protocol HTTP/1.1) section 3.2.1 says
The HTTP protocol does not place any a priori limit on the length of a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15).
Note: Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations might not properly support these lengths.
There's two limits under discussion here. I answered by how much data can be sent back to the browser. The posters talking about limits are referring to data sent to the server. Which were you asking about?
The specification does not limit the size of a POST/GET request.
But since GET resquest parameters names and values are embeded in the input url, and the input parameters of the post section
are located in the body section of the input xml, some problem may occurs with older browser with some request, since they limit
url to 255,512 or 1024 characters.