I have an agent on a web site which calls a form by doing a Print “[/something/mybase.nsf/myForm?ReadForm&p1=a&p2=y&p3=2]”
In total I have 55 of these “px=” parameters.
This worked fine on Domino 5.0.10, but when I upgraded the server to Domino 6.5.1 CF1 I get this error message when the agent runs:
HTTP Web Server: Invalid URL Exception
I have tried changing the agent to see if the length of the URL is too long. This seems to have no bearing on the subject, however if I limit the number of parameters to 32 it works fine.
Does anyone know of a setting I can use to allow more than 32 parameters in the URL?
I have tried increasing the values under “HTTP Protocol Limits” in the server document, but no luck.
Any help would be greatly appreciated!
Subject: Invalid URL Exception when having more than 32 parameters
It may be the length of that particular url based on the total character count of the values. I believe R6 URL max size is 2048 characters.
One idea. Just pass the UNID of the source (original) doc in your url. You can then look it up in the target form by unid and get all your parameters from it.
Subject: I don’t think that’s it…
If the URL fragment in the original post is reflective of the actual argument string used, I doubt very seriously that it is the total URL length. Each argument in the example has only five characters (including the & separator). Multiply by 55 arguments and that leaves you with a grand total of 275 characters in the argument. Unless the other text in the URL is something like 1800 characters (highly unlikely, I’d say), it’s very, very hard to imagine that overall URL length is the culprit.
Subject: Thanx for your replies.
I did as you suggested, Chuck, and of course that works fine :o)
I think you’re right about the URL length to, as my URLs contain far less than 2048 characters.
I’m going with the option of rewriting these agents so that they don’t contain the ‘&’.
THANKS FOR YOUR HELP CHUCK AND CHARLES 
Tormod
Subject: RE: Thanx for your replies.
Tormod, I’m more than happy to help and glad that you’ve got a workable solution!
Subject: RE: Invalid URL Exception when having more than 32 parameters
The maximum URL length is settable on the server document (Internet Protocols → HTTP tab → HTTP Protocol Limits). It is possible that the server doc setting does not allow a URL long enough to pass the GET, but it’s not an inherent limit.
I’m with Chuck, though – I’d POST this much data rather than GET.
Subject: Invalid URL Exception when having more than 32 parameters
Tormod, are you really sure you want to pass that many arguments in the URL? Why not just send one or a few concatenated string arguments which you could then parse in the WebQueryOpen event of that form? Am I missing something?