I have a VB client app and a classic ASP page.

The app sends a very long string in the query string to the asp page.

[code]http://www.xyz.com/clientresp.asp?clp=sfhsdahfaffasfasafasfffasffafas fsf....[code]

When I read the query string value like in asp:

strVal = request("clp")

response.write(strVal)

I get nothing. I even tried writing the strVal to a text file with no success. I am positive my query string value is too long. There was a registry hack to make the IIS accept longer query string values. Any help is appreciated.

Thanks

How long is 'very long'? I am intrigued to know if there is a max length

Are other querystrings working? Have you trimmed the length to see if length is your problem? I would do this. If I found length was my problem I would pass the value another way

I have never known what is considered to long. If there is a suggested maximum length I would abide by it.

__________________
Wind is your friend
Matt

IIRC, when the query string size was above 2kb, I started to get empty values. I had to do a registry hack to increment the size. I moved the asp page to a brand new windows 2003 server recently and I ran into the problem like I did with the old server. I forgot what I did for the old server. I know I could use POST.

2kb cant imagine how you even get this measure. I would expect to hear about charcter length when talking about QS size. Sounds like you need to use a more suitable method of passing values.

If you must try to make it work you would need to edit a property in the metabase.mxl file on a 2003 server

__________________
Wind is your friend
Matt

Thanks.

I need to expand the size limit using the AspMaxRequestEntityAllowed metabase property.

http://www.microsoft.com/technet/pro....mspx?mfr=true

Im still intrigued to know the charcter limit where it becomes unhappy? I cant see me ever reaching it but it would be interesting to know, not to mention good for other users in the Wrox knowledge base

__________________
Wind is your friend
Matt

It is a *BROWSER* limitation, typically. And though modern browsers seem to allow 1KB or more, you should NEVER count on more than 512 characters. And, remember, that is the *encrypted* length. (That is, a space encoded as %20 counts as 3 characters.)

But if you have one page that is directly hitting some web server, where no browser is involved, it shouldn't matter much. Still, it would have been better to use POST data instead of GET data (a querystring is GET data).