That would be nice. It would have to be an IIS box configured so that:
* http://www.example.com/ does not support WebDAV (or everything is forbidden)
* http://www.example.com/webapp/ supports WebDAV, but everything is forbidden
* http://www.example.com/webapp/webdav/ supports WebDAV with DIGEST authentication.
I actually have different webdav/realm/ subdirectories, so it doesn't even make sense for me to authenticate in the parent directories---there would be no valid realm for me to send as a DIGEST challenge! (This is why it's so crazy---and potentially show-stopping---that MS Web Folders is even accessing directories up the hierarchy.)
Garret
Parsons Technical Services wrote:
Does anyone have an IIS box you can connect to to see what happens. Then maybe you can mimic it.
Doug
----- Original Message ----- From: "Garret Wilson" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[email protected]>
Sent: Tuesday, January 11, 2005 1:12 PM
Subject: Re: Apache, Tomcat, WebDAV, and Web Folders... Oh, my!
Yeah, that's what I *assume*, anyway. But Ethereal doesn't work on localhost, so I can only assume. There are these possibilities:
* Tomcat returns something other than 501 Not Implemented when configured on localhost. (Not likely.)
* MS Web Folders does different checks when accessing the Internet-at-large than when accessing localhost. (Likely? I don't know what to expect with MS Web Folders anymore.)
I'm guessing the latter is happening, especially as two MS user agents get into the act: "Microsoft-WebDAV-MiniRedir/5.1.2600" and "Microsoft Data Access Internet Publishing Provider Protocol Discovery"
And here's more news: I created a new DefaultServlet mapped to "/" that for PROPFIND simply returns 403 Forbidden. Something different happens. First, "Microsoft-WebDAV-MiniRedir/5.1.2600" does a PROPFIND on /webapp (which gets redirected to /webapp/). MyDefaultServlet returns 403 Forbidden. Fine. Can you guess what "Microsoft-WebDAV-MiniRedir/5.1.2600" does?
"Microsoft-WebDAV-MiniRedir/5.1.2600" then tries to do another PROPFIND on /webapp! And another---for a total of five times! (It's forbidden, you idiot---and /webapp is none of your business anyway; you're supposed to be accessing /webapp/webdav/! Arggg!!!)
Then "Microsoft Data Access Internet Publishing Provider Protocol Discovery" comes along and does its little OPTIONS / (200 OK) OPTIONS /webapp/webdav (401 Unauthorized) dance for three times, and then goes into the FrontPage mumbo-jumbo.
What is left to do---issue a 401 Unauthorized on PROPFIND /webapp ? Issue a 401 Unauthorized on OPTIONS / ? Rewrite the operating system? (Yeah, the latter is probably what I'll have to do to fix all this mess.)
(Grumble grumble grumble...)
Any suggestions on what to do next?
Garret
Varley, Roger wrote:
About the only thing left to try is to allow the PROPFIND on /webapp/ . So here's the Tomcat question---how can I allow a PROPFIND on /webapp/ and return, for example, a 403 forbidden, rather than a 501 Not Implemented? Do I have to override org.apache.catalina.servlets.DefaultServlet? (There goes container independence.)
But surely Tomcat returns 501 when accessed via Localhost and you've already said that scenario works.
Regards Roger
__________________________________________________________________________
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
__________________________________________________________________________
--------------------------------------------------------------------- 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]
