Just curious why this case is implemented inside POST when it only uses the
url to determine it's behavior and ignores the POST content? Shouldn't this
be another case to use on GET? I do realize the casing would be a little
complicated so maybe that was the reasoning.
The reason I ask is because I can see the use case where I have precompiled
xquery in the db and want to apply in on a resource and have the results run
through an xslt, or provide an xpath to operate on the resource(s) and then
have those handed to the precompiled xquery.
These use cases arent supported because there is no room for extra
parameters as is. One solution to stay back-compatible is to simply read
the POST body even in this case and allow the additional parameters to be
Thoughts? maybe I'm missing something... wouldn't be the first time.
Get latest updates about Open Source Projects, Conferences and News.