It's usually the client that cuts things off... And IIS will too at some point. This is what all those buffer overrun URLs are trying to accomplish to stuff text into the system buffers by overrunning that buffer.

Either way, it's a bad idea to send that much data on the querystring. If you're sending this amount put in the POST buffer...

+++ Rick ---



>>HTTP spec officially puts a limit of 512 bytes for the querystring. Most browsers however do not use that - IE is about 2k. Servers shouldn't care assuming buffers are not overrun (that's what Code Red has been all about).
>
>My post (no pun intended) was based on this excerpt from the HTTP/1.1 spec:
>
>RFC 2616 HTTP/1.1
>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. 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).
>
>Is there a limitation imposed elsewhere, or are we talking apples and oranges?
>
>>Are you saying on the server? I don't think so... IIS's first input buffer is 49k by default - POST data can be of any size per spec, so if there's an issue it's most definitely on XMLHTTP. I've sent more data than that with it, so I'm pretty sure that this works.
>
>I have encountered length limits in the past, but where the problem was is fuzzy in my mind. SQL XML' IIS extension imposes a POST limit...that could be where my crazy idea comes from...
>
>Daryl