There is also a clarification draft for HTTP available:
http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p1-messaging-05.txt
HTTP does not place an 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 9.4.15 of [Part2]).
Daniel-Constantin Mierla wrote:
On 11/26/08 09:45, Pascal Maugeri wrote:
AFAIK there is no limit fixed by RFCs.
Nevertheless the limit is fixed either by browers or servers implementations. e.g. firefox is repported to work with URL > 65K characters but is seems to be a limit in Apache server :-/
Check this link: http://www.boutell.com/newfaq/misc/urllength.html
I expect that some firewall or intrusion detection system will complain about long URL too.
in this case it is even shorter, because of internals in kamailio - so it can be up to 1024 now.
Cheers, Daniel
-pascal
On Wed, Nov 26, 2008 at 1:07 AM, Juha Heinanen <jh@tutpro.com mailto:jh@tutpro.com> wrote:
--text follows this line-- I ñaki Baz Castillo writes: > Sure, I'm just asking about possible limitations in a GET query (when being > too long) since I don't know a lot about HTTP protocol. i don't know what the max size of url is. there must be an rfc that tells it. in my tests with a few uris as parameters, i have not hit the limit yet. -- juha _______________________________________________ Users mailing list Users@lists.kamailio.org <mailto:Users@lists.kamailio.org> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users