Chaohua Wang wrote:
Thank you, the servlet server doesn't handle this request, so I can't see any log info. I have found the url string is too long because of too many parameters. There is a fairly small limit on the number of bytes you can send in a GET request, 256 characters (approx.) there is any set up can fix this long string url issue.
The rfc only state: "Servers MUST be able to handle the URI of any resource they serve". This means that you can not rely on the server handling long urls. A well behaving server ought to answer with something reasonable, like a "200 OK" or a "414 Request URI Too Long", a "500 Internal Server Error" is probably ok as well (from the point of the rfc). Crashing and closing the connection is not valid. If this is what happens to you, then it looks like you have a non-http/1.1 compliant server. You might want to tell the admins to fix it. Without a wirelog it is hard to tell exactly what happen. Last time I checked you could change the url length for apache at compile time and the default was something like 2kB. Since you do not say what server this is it is not possible to say how you can change the server. What can you do? 1) Change the request to a POST. If you risk having long queries you really should use POST instead. 2) Change the request parameters so that it is shorter. As it looks now you could perhaps change it into something like: (tblCase.CaseTypeCode between 210000 and 210020 or...) 3) Change the server so that it accepts longer uri:s. Could be problematic if you are not the admin of the server. Might mean a code change and a recompile even if you are the admin. /robo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
