Pradeep Shekade wrote:
>
> I guess the limit with GET is 2k
>
I guess it isn't. Please, can we end this?
There isn't a single, fixed limit. What rfc2616 says
(about servers, not clients) is:
3.2.1 General Syntax
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.
But that's not how it actually works in the real
world. Various tools (browsers, servers, proxies)
have different limits. As Gokul Singh pointed out,
the http spec (rfc2616, please get it and read it)
suggests 255 as a safe upper limit. Most browsers
handle somewhat more than this.
On the server side, Apache, Tomcat and Squid have
an upper limit as a compile time constants.
There are legitimate reasons to use very long URLs
in GETs, but it's an advanced topic and you have to
be hyper-aware of the limitations. Basically, if you
have to ask, then you should just use POST.
-cks
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html