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=28140>. 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=28140 Problems when WebDAV servlet is not the default servlet ------- Additional Comments From [EMAIL PROTECTED] 2004-05-07 15:49 ------- Just tried the new 2.0 release and it looks like many of the serverURL- >servletPath issues were resolved. But there are several still lurking about. I'm going to attach a sample input/output using Windows Webdav support. I would assume that Webdav is consistent with hrefs in that they should be including the contextPath/servletPath everywhere. Highlights that I think are wrong are: 1) No contextPath/servletPath <D:href>/roles/HAB_Admin</D:href> 2) No servletPath <D:href>/hab-samples/users/unauthenticated</D:href> 3) Null servletPath <D:href>/hab-samplesnull/users</D:href> There are 4 occurances of "null, sConf" in PropertyHelper which I think is the null problem. I had suggested before about condensing passing context path and servlet path into just passing in the request. Many places pass "String servletPath, String contextPath", whereas the WebdavUtils.getAbsolutePath takes "String contextPath, String servletPath". You know somewhere these are or will be reversed. Conceptually at least these should be reversed as context path comes first, then servlet path. But, I think converting to request will be much less error prone. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
