You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2015/09/01 12:50:45 UTC
[jira] [Updated] (SLING-4976) Clarify handling of empty JCR
workspace name in WebDAV URLs
[ https://issues.apache.org/jira/browse/SLING-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated SLING-4976:
---------------------------------------
Description:
The handling of an empty JCR workspace name in WebDAV URLs has changed recently, I'll create an integration test that demonstrates the changes.
_Update: the change in behavior is apparently caused by upgrading to org.apache.felix.http.jetty/3.1.0, see SLING-4978_
was:The handling of an empty JCR workspace name in WebDAV URLs has changed recently, I'll create an integration test that demonstrates the changes.
> Clarify handling of empty JCR workspace name in WebDAV URLs
> -----------------------------------------------------------
>
> Key: SLING-4976
> URL: https://issues.apache.org/jira/browse/SLING-4976
> Project: Sling
> Issue Type: Task
> Components: Servlets
> Affects Versions: JCR Webdav 2.3.0
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: JCR Webdav 2.3.2
>
>
> The handling of an empty JCR workspace name in WebDAV URLs has changed recently, I'll create an integration test that demonstrates the changes.
> _Update: the change in behavior is apparently caused by upgrading to org.apache.felix.http.jetty/3.1.0, see SLING-4978_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)