DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37511>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37511 Summary: WebdavResource quashes queryString Product: Slide Version: 2.1 Platform: All OS/Version: other Status: NEW Severity: major Priority: P2 Component: WebDAV client AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] 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? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
