You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2008/10/02 15:45:47 UTC
[jira] Created: (JCR-1782) Destination header not containing URI
scheme causes NPE
Destination header not containing URI scheme causes NPE
-------------------------------------------------------
Key: JCR-1782
URL: https://issues.apache.org/jira/browse/JCR-1782
Project: Jackrabbit
Issue Type: Bug
Components: jackrabbit-webdav
Reporter: Julian Reschke
Priority: Minor
In WebDAVRequestImpl. getDestinationLocator assumes that URI.getAuthority is always non-null.
In RFC2518, a full URI is indeed required, but the NPE causes a status of 500, instead of 400 as expected.
In RFC4918, an absolute path is allowed.
Proposal: delegate to gethrefLocator, which already does the right thing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1782) Destination header not containing URI
scheme causes NPE
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-1782:
------------------------
Fix Version/s: 1.5
> Destination header not containing URI scheme causes NPE
> -------------------------------------------------------
>
> Key: JCR-1782
> URL: https://issues.apache.org/jira/browse/JCR-1782
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-webdav
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 1.5
>
>
> In WebDAVRequestImpl. getDestinationLocator assumes that URI.getAuthority is always non-null.
> In RFC2518, a full URI is indeed required, but the NPE causes a status of 500, instead of 400 as expected.
> In RFC4918, an absolute path is allowed.
> Proposal: delegate to gethrefLocator, which already does the right thing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JCR-1782) Destination header not containing URI
scheme causes NPE
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke reassigned JCR-1782:
-----------------------------------
Assignee: Julian Reschke
> Destination header not containing URI scheme causes NPE
> -------------------------------------------------------
>
> Key: JCR-1782
> URL: https://issues.apache.org/jira/browse/JCR-1782
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-webdav
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
>
> In WebDAVRequestImpl. getDestinationLocator assumes that URI.getAuthority is always non-null.
> In RFC2518, a full URI is indeed required, but the NPE causes a status of 500, instead of 400 as expected.
> In RFC4918, an absolute path is allowed.
> Proposal: delegate to gethrefLocator, which already does the right thing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1782) Destination header not containing URI
scheme causes NPE
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-1782.
---------------------------------
Resolution: Fixed
Fixed with revision 701129.
> Destination header not containing URI scheme causes NPE
> -------------------------------------------------------
>
> Key: JCR-1782
> URL: https://issues.apache.org/jira/browse/JCR-1782
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-webdav
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
>
> In WebDAVRequestImpl. getDestinationLocator assumes that URI.getAuthority is always non-null.
> In RFC2518, a full URI is indeed required, but the NPE causes a status of 500, instead of 400 as expected.
> In RFC4918, an absolute path is allowed.
> Proposal: delegate to gethrefLocator, which already does the right thing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.