sling-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Klimetschek <aklim...@day.com>
Subject Re: Problem with encoded URL
Date Tue, 07 Sep 2010 09:04:59 GMT
On Tue, Sep 7, 2010 at 09:33, Class, Jakob <jakob.class@siemens.com> wrote:
> Hi!
>
> Can someone tell why http://localhost:8080/jcr:system.json works, but http://localhost:8080/jcr%3Asystem.json
does not? Do I have to configure something to get it work?

The Sling-style encoding for those prefixes is like /_jcr_system.json.
This is because file-system based caches mostly won't work with either
":" or "%" in a file name. You get those encodings when using
ResourceResolver.map() to create relative links.

I don't know why %3A doesn't work, I think it should.

Regards,
Alex

-- 
Alexander Klimetschek
alexander.klimetschek@day.com

Mime
View raw message