JR added the WebDAV HTTP methods to Rife, and my setup is using them.
Heh, well, I added them ;-)
However it is still the case that: I can access a particular content item in a browser with a plain old HTTP URL and it executes my Rife code and I can pipe the content into the output stream and it just works, but when I try to "open" the same URL with WebDAV, _no_ Rife code is executed. Not even any of the new, added WebDAV methods are detected and passed to my code. Therefore I suspect that the editor is first trying to authenticate itself using an HTTP-based mechanism which is unfamiliar to (i.e. unimplemented by) Rife.
Why don't you setup a HTTP monitor and proxy to track what's really going on, like that you know, we can trace it and make sure that everything goes through to RIFE.
Thus my motivation for handing off authentication chores to Tomcat. However, this suspicion (that the editor is trying to authenticate itself using HTTP) is still unverified. Another possibility of course is that JR's code contains bugs. But, I would expect to see a proton decay before I saw that ;-)
I'd be very surprised to see a but appear in the handling of the additional HTTP methods, they are just additions to a type-safe enum. I even made the enum self-adapting in case other methods pop up.
-- Geert Bevin Uwyn bvba "Use what you need" Avenue de Scailmont 34 http://www.uwyn.com 7170 Manage, Belgium gbevin[remove] at uwyn dot com Tel +32 64 84 80 03 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net _______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
