Bug 37511 - WebdavResource quashes queryString
Summary: WebdavResource quashes queryString
Status: NEW
Alias: None
Product: Slide
Classification: Unclassified
Component: WebDAV client (show other bugs)
Version: 2.1
Hardware: All other
: P2 major (vote)
Target Milestone: ---
Assignee: Slide Developer List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-15 18:34 UTC by Keith Berard
Modified: 2005-11-15 09:34 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Keith Berard 2005-11-15 18:34:08 UTC 
This is for package: jakarta-slide-webdavclient-bin-3.1

In the org.apache.webdav.lib.WebdavResource class, the calls to extension
methods (Lock, Unlock, etc) first make a call to URIUtils.encodePath().   This
path is sent to each super constructor till it meets HttpMethodbase. 
HttpMethodBase is able to get access to the queryString, but the path now sent
no longer has a ? to split upon.

Because of this, calls to GET and PUT accept a queryString (eg: session
authentication) but calls to the WebDav extensions (LOCK, UNLOCK) do not.

Calling new LockMethod(...) manually does not exhibit this problem, because
URIUtils.encodePath() is not called.

Is this intentional behavior?  If so, why is it only enforced in WebdavResource?