I am having the following problem :
I created a service to call a lotusscript agent with a service.
When I test from the service configuration, it's ok, the agent runs and returns a json response.
When this same service is run from a Volt application event (Submit button), this causes an error.
Also, the following error message appears on the server console:
"HTTP Web Server: Invalid URL Exception [/C125861F004B33EF/myagent?id=cccad484-8c5d-4f1d-8ff8-f03e8c089abf]"
We notice that the "openagent&" part has disappeared from the url
If anyone managed to call a lotusscript agent from Volt, I'm a taker, thank you very much for your help !!!
I just redid the tests in a very basic application.
The context of use is a button in the form that calls the service.
The error is caused by the use of parameters or not in the url.
"https://myvolt.legroupenova.com/C125861F004B33EF/myagent?openagent": works
"https://myvolt.legroupenova.com/C125861F004B33EF/myagent?openagent¶m=test": works when configuring the service but error when using:
"HTTP Web Server: Unknown Command Exception [/C125861F004B33EF/myagent?param=test]"
I see the same problem on the server console : "openagent&" part has disappeared from the url
Obviously DLeap removes all HTTP GET parameters from the URL. Not sure whether it is a bug or an intention, but in general they should work:
The REST specification does not explicitly mandate or restrict the use of HTTP GET parameters in the URI. This means that parameters can be included in the URI to identify resources or to provide filtering, sorting, or other query capabilities. Using HTTP GET parameters in the URI is a common practice and aligns with REST principles as long as it adheres to the following:
- Resource Identification: The URI should uniquely identify the resource.
- Statelessness: Each request from the client to the server must contain all the information the server needs to fulfill the request.
- HTTP Methods: Use GET for safe and idempotent operations (i.e., operations that do not modify the resource).
IMO you should open a support case.
This error still persists. Has there been no ticket for this?
It's currently not possible to call webbased domino agents with parameters because
the service cuts of the "?OpenAgent" part which results in a error 400.
It's just as described in the sample...
We have a default setting that ignores empty url parameters. The "openAgent" is being evaluated as a url parameter that has no value and so it is being excluded from the run-time call.
It would seem that the use of "openAgent" does not really adhere to common practices. It looks like I would have to make some kind of exception for that specific string.
