My mind was playing tricks on me. My last reply wasn't accurate. I'll do more research. Thanks for the clarification.
Brian ----- Forwarded by Brian K Bonner/paraware on 11/19/2004 03:40 PM ----- Brian K Bonner/paraware wrote on 11/19/2004 03:37:01 PM: > That sounds like what I'm seeing. IE 6 is not redirecting. Thanks > for the clarification. :) > > Brian > > "Mark Thomas" <[EMAIL PROTECTED]> wrote on 11/19/2004 03:02:58 PM: > > > From what I recall, TC4 forwards to the index page whereas TC5 sends > > a redirect. > > I am sure one of the other committers will correct me if I am wrong here ;) > > > > You then get into exactly how the mappings, welcome files etc are > > processed and > > in what order. Off the top of my head, I don't recall the details - > > the spec is > > the best place to check up on this sort of thing. > > > > Mark > > > > FYI The issue with MS clients is that they don't handle redirects to > > well (or at > > all even...) > > > > > -----Original Message----- > > > From: Brian K Bonner [mailto:[EMAIL PROTECTED] > > > Sent: Friday, November 19, 2004 7:21 PM > > > To: Tomcat Users List > > > Subject: RE: WebDav behavior > > > > > > Mark, > > > > > > I understand the issue w/ contexts (and I believe I > > > understand the issue > > > w/ not being able to handle JSPs), **but I don't understand > > > why the base > > > behavior is different**. > > > > > > Are you suggesting that the 4.1.x, 5.x is causing a difference in the > > > Webdav behavior that would prevent http://localhost:8080/webdav from > > > displaying the index.html file? > > > > > > I noticed that the comment on servlet-mapping indicates > > > something to this > > > effect, but from what I read I understood it to be more for > > > rogue clients > > > (i.e. MS Webfolders). > > > > > > I'm only trying to work w/ Static content now, and I recall > > > reading that > > > webdav servlet won't work w/ .JSP files IIRC because of how > > > the content is > > > served up. > > > > > > Thanks, > > > > > > Brian > > > > > > > > > > > > "Mark Thomas" <[EMAIL PROTECTED]> wrote on 11/19/2004 01:57:01 PM: > > > > > > > The webdav servlets are exactly the same, give or take a > > > few formatting > > > > differences. > > > > > > > > There are difference between 4.1.x and 5.x in how requests for > > > > http://host/webapp/ are handled. > > > > > > > > Generally, you can use a context for webdav, or you can use it with > > > > a browser to > > > > server content. Trying to mix the two usually results in a > > > headache of > > > some > > > > form. That said, if you only want to serve static content, whilst > > > > retaining the > > > > ability to edit it via webdav there are people out there that do > > > > this. The exact > > > > configuration tends to depend on the TC, browser and webdav client > > > combination > > > > you choose. Search the archives for tips. > > > > > > > > Mark > > > > > > > > > -----Original Message----- > > > > > From: Brian K Bonner [mailto:[EMAIL PROTECTED] > > > > > Sent: Friday, November 19, 2004 6:12 PM > > > > > To: [EMAIL PROTECTED] > > > > > Subject: WebDav behavior > > > > > > > > > > I've recently installed WebDAV app as part of a 5.0.27 and > > > > > 5.5.54 install. > > > > > I also have it installed on 4.1.29. > > > > > > > > > > When I access a page from a browser (e.g. Firefox), via: > > > > > http://localhost:8080/webdav on 4.1.29, it returns to me > > > the page at > > > > > http://localhost:8080/webdav/index.html. > > > > > > > > > > When I do the same on 5.0.27 or 5.5.54, I get a directory listing. > > > > > > > > > > I added the welcome files to the 5.x installs as follows: > > > > > > > > > > <!-- Establish the default list of welcome files --> > > > > > <welcome-file-list> > > > > > <welcome-file>index.jsp</welcome-file> > > > > > <welcome-file>index.html</welcome-file> > > > > > <welcome-file>index.htm</welcome-file> > > > > > </welcome-file-list> > > > > > > > > > > And still I get the directory list. > > > > > > > > > > > > > > > If I try to access the content using DAVExplorer, I can read > > > > > and write > > > > > all of the content on any of the environments. > > > > > > > > > > If I try changing the servlet mapping to: > > > > > > > > > > <!-- The mapping for the webdav servlet --> > > > > > <servlet-mapping> > > > > > <servlet-name>webdav</servlet-name> > > > > > <url-pattern>/</url-pattern> > > > > > </servlet-mapping> > > > > > > > > > > on 5.x (to make it similar to that of 4.1.29) > > > > > > > > > > from: > > > > > > > > > > <!-- The mapping for the webdav servlet --> > > > > > <!-- Using /* as the mapping ensures that jasper, welcome > > > > > > files etc are > > over-ridden and all requests are > > processed by > > the > > webdav servlet. > > This also > > overcomes a number of > > issues with some webdav clients > > > > (including MS Webfolders) > > that do not respond correctly > > to > > the > > redirects (302) > > that result from using a > mapping of / --> > > > > > <servlet-mapping> > > > > > <servlet-name>webdav</servlet-name> > > > > > <url-pattern>/*</url-pattern> > > > > > </servlet-mapping> > > > > > > > > > > it displays the page correctly, but then in DAVExplorer, I > > > > > only see the > > > > > one file. > > > > > > > > > > Is there something special I need to do w/ the default > > > > > install to have it > > > > > redirect the browser to the Welcome page? Is there WebDAV > > > > > servlet under > > > > > 5.x substantially different than 4.1.29 that would cause this > > > > > behavior > > > > > change? > > > > > > > > > > Thanks, > > > > > > > > > > Brian > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
