You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@sling.apache.org by "Class, Jakob" <ja...@siemens.com> on 2010/09/07 09:33:21 UTC

Problem with encoded URL

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?

Regards
Jakob

Re: Problem with encoded URL

Posted by Alexander Klimetschek <ak...@day.com>.

On Tue, Sep 7, 2010 at 09:33, Class, Jakob <ja...@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