|
From: Vic M. <vic...@gm...> - 2011-10-27 21:03:33
|
Hi,
I have an XQUERY that takes multiple parameters. When I call
http://myhost/exist/rest//db/cache/cachetill.xq?expiration=10*&*url=<some
encoded url>
it works fine and I get back the requested XML data (some context: this
XQUERY is building a cache).
When I call the same URL, but with parameters separated by "&", no data
is returned at all:
http://myhost/exist/rest//db/cache/cachetill.xq?expiration=10*&*url=<some
encoded url>
I tested this with different browsers (Chrome, Firefox, even linux 'wget'),
and it's all behaving the same.
It's very strange, because I've got other XQUERY's that take multiple
parameters and that don't care about the & vs. &.
This is the complete URL:
http://ec2-46-137-56-166.eu-west-1.compute.amazonaws.com:8080/exist/rest//db/cache/cachetill.xq?expiration=10
*&*
url=http%3A%2F%2Fchildrensmissal.appspot.com%2FgetCoordinates%3Fdate%3D2011-09-05%26options%3Depiphany-alt%2Ccorpuschristi-std%2Cascension-std%26score%3Dyes%26output%3Dxml<http://ec2-46-137-56-166.eu-west-1.compute.amazonaws.com:8080/exist/rest//db/cache/cachetill.xq?expiration=10&url=http%3A%2F%2Fchildrensmissal.appspot.com%2FgetCoordinates%3Fdate%3D2011-09-05%26options%3Depiphany-alt%2Ccorpuschristi-std%2Cascension-std%26score%3Dyes%26output%3Dxml>
UPDATE while writing: I tried to request the same REST query, but with the
parameters in different order, and now it works!! Is there something in the
encoded URL parameter that gives XQUERY the hick-ups?
I guess I'll get around this now, but maybe it's worth investigating?
Groeten,
Vic
--
Vic Mortelmans
Klappeistraat 34A - 2060 ANTWERPEN
03 297 40 23 - 0499 71 06 37
|