You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "David Caruana (JIRA)" <ji...@apache.org> on 2010/01/13 19:06:54 UTC
[jira] Commented: (CMIS-97) Deal with encoded paths in URI
templates
[ https://issues.apache.org/jira/browse/CMIS-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799851#action_12799851 ]
David Caruana commented on CMIS-97:
-----------------------------------
This is the approach of Alfresco too. I agree, the uri path version is nicer.
> Deal with encoded paths in URI templates
> ----------------------------------------
>
> Key: CMIS-97
> URL: https://issues.apache.org/jira/browse/CMIS-97
> Project: Chemistry
> Issue Type: Improvement
> Components: atompub, server
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
>
> Tomcat since 6.0.10 by default forbids any URL containing a %2F (for some dubious security reasons to be robust against broken proxies).
> To allow them you have to start your Tomcat with:
> -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true
> See http://tomcat.apache.org/security-6.html#Fixed%20in%20Apache%20Tomcat%206.0.10 for more.
> But it's it's too problematic to ask people running Chemistry server code to use -Dsomething at Tomcat startup, so let's change Chemistry to use .../object?path={path} for path-based addressing.
> It's less elegant but then again there's no way to advertise clean path building like http://host/cmis/path/folder1/folder2/foo, they just can't be constructed using CMIS 1.0 URI templates, which MUST be encoded (which doesn't prevent us from accepting them however).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.