Bug 34726

Summary: "response already committed" during LOCK operation...
Product: Slide Reporter: Gregory Block <gblock>
Component: WebDAV ServerAssignee: Slide Developer List <slide-dev>
Status: NEW ---    
Severity: normal    
Priority: P2    
Version: Nightly   
Target Milestone: ---   
Hardware: Other   
OS: other   

Description Gregory Block 2005-05-03 18:56:56 UTC
TP-Processor2, 03-May-2005 17:51:03, gblock@ctoforaday.com, LOCK, 200 "OK", 24 ms, /clients/istc/
03-May-2005 17:51:03 org.apache.jk.server.JkCoyoteHandler action INFO: Response already 

Conveniently, I'm also now having a problem using Dreamweaver and GoLive not being able to unlock 
files properly - I'm wondering if the reason I'm having that problem is now associated with the above.

Can someone familiar with the webdav servlet give me some idea of where to look, here?  Looks like 
something has happened to cause the servlet to start sending its output before we're ready with the 
lock response headers; perhaps setting the response code before the headers are ready?