On 7 Jul 2010, at 14:25, Alexander Klimetschek wrote: >> That would allow listing of all the users. > > Ah, right, now I am finally getting to the point of this discussion ;-).
Thats probably down to my poor explanation, sorry. > > In this case I would give the /content/users node an explicit resource > type and override all the default get servlets from sling that allow > listing of that resource in json, xml, webdav etc. to prevent that. > Which is more or less what was suggest before, I guess :) Unfortunately /content.2.json gets round that. Ian
