Surely sendmail reeled when thusly spake Geert Bevin: > > AFAIK Tomcat authentication should just work. > > I however don't fully understand what benefit you would get from it, > besides the downside of tying your authentication scheme to one > particular servlet container.
That is true. > I suppose I'm missing something, can you give me pore details about > what it would bring you over RIFE's authentication? JR added the WebDAV HTTP methods to Rife, and my setup is using 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. 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 ;-) fred _______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
