Windows 2k bug

[Peter Hawkins <pe...@globalvision.com.au>]

Just thought I'd let you all know something I've discovered and placed on
the FAQ. Slide won't work with the version of IE that ships with W2K so that
a vanilla W2K install with TC and slide fails.

I've tracked it down to the web folders DAV client that comes with IE5.0 -
it sends credentials for every request but not the HEAD method request it
issues just before a file upload. Upgrading to IE5.5 sp1 fixed it.

I checked the MS knowledgebase but couldn't identify any PR that seemed to
be the one, however it's fixed with IE5.5, so no matter. Still, it's a bit
of a trap!

To see it, install W2K out of box, add TC4b3, add a user for root in TC's
users file, drop in the slide.war, run TC (to unpack the war) then edit
slide's web.xml to allow auth. Restart TC and create a web folder. You'll be
able to create a sub-folder but not upload a file. To see why, set your TC
for logging and debugging and look in the TC log file - no credentials for
HEAD, so TC doesn't pass the HEAD through to slide at all.

Peter

WebDAV client API change

[Remy Maucherat <re...@apache.org>]

Hi,

The WebDAV client library is about to be split in two parts (the reasons for
this are given below) :
- All the HTTP/1.1 specific code is moved to the commons subproject. The
rationale is to make it easier for other projects (like Tomcat) to reuse the
code.
- The WebDAV specific part of the client library will extend that HTTP/1.1
core, and will remain in Slide.

IMO, that's the best way to keep Slide focused on its core goals (WebDAV and
content management), while allowing more people to develop the HTTP library
independently.

The API changes this causes are :
- Some classes are renamed :
  WebdavClient -> HttpClient
  WebdavException -> HttpException
  WebdavStatus -> HttpStatus
- A lot of the classes in the lib package are moved to package
org.apache.commons.httpclient

Comments ?

Note : To minimize the time needed to update any existsing application to
the new API, I can introduce some "fake" objects (for example, add back a
WebdavClient object which would directly extend the new HttpClient object).
This would almost allow full API backwards compatibility. Please let me know
if you think this would be needed.

Thanks,
Remy