before you ask what I would like to accomplish with many web requests :smileywink:, let me explain some situations where many web requests may be necessary:
- a situation where a user stores found sets in a history and later wants to combine those sets by boolean logic; then the record ids must be combined to a new query (another way would be to combine the stored queries, but that may fail)
- a situation where a user manually picks records in a found set and wants to use them for another action; then individual record numbers must be queried
tests by Allan Hunter (see Techtalk list) have shown that with the client, several 10'000 requests can be submitted in a compound query. So no problem there.
However, the story is different for Custom Web Publishing, as my tests show. The limitation is set by the maximum length of the query URL, which for a HTTP GET seems to be 1024 characters.
This limits the number of requests for an OR compound query to a maximum of about 30, depending on the string length of the individual query values.
Test files can be downloaded here.
The funny thing is that the test runs through even for 100 requests and all query URLs are logged in the web server log, but the CWP does not respond with a result set or an error message if the length of the GET request is exceeded.
This size limit of 1024 for a GET request is too low to write an efficient algorithm for the situations depicted in the previous post.
Is there any way to set allowed URL size for a GET request in the web server or the Tomcat part of the Web Publishing Engine, or is this hardcoded in the Web Publishing Engine?
Thank you for the explanation and example.
I have forwarded the entire thread along with the sample file(s) to our Development and Software Quality Assurance (Testing) departments for review and confirmation. When I receive more information and/or an answer to your question, I will let you know.