I created a JIRA at https://issues.apache.org/jira/browse/SLING-1308
for this issue
with the correct patch attached to it.
Regards,
Simon
On 20 Jan 2010, at 23:17, Alexander Klimetschek wrote:
On Mon, Jan 18, 2010 at 18:32, Simon Gaeremynck
<[email protected]> wrote:
Downside of setting the Location header is that most client's will
automatically retrieve their data.
For example doing a GET request with jquery in firefox
to /.infinity.json
will automatically
result in a second request to /.2.json
Ah, that might be considered good or bad ;-) In order to provide
against possible DOS attacks, generating a second request with the
maximum number allowed definitely creates too much unnecessary new
load. Maybe it's better then to keep it just as json array in the
body. A proper client would need to handle it manually anyway to get
all the json he wants, if there is a limit. For example, requesting
/.infinity.json or /.4.json where the limit is at /.2.json requires
him to fetch the content level-by-level anyway...
Regards,
Alex
--
Alexander Klimetschek
[email protected]
