Bug 34726 - "response already committed" during LOCK operation...
Summary: "response already committed" during LOCK operation...
Status: NEW
Alias: None
Product: Slide
Classification: Unclassified
Component: WebDAV Server (show other bugs)
Version: Nightly
Hardware: Other other
: P2 normal (vote)
Target Milestone: ---
Assignee: Slide Developer List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-03 18:56 UTC by Gregory Block
Modified: 2005-05-03 10:56 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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/
stb/img/bt_produtos_country_brasil.gif
03-May-2005 17:51:03 org.apache.jk.server.JkCoyoteHandler action INFO: Response already 
committed 

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?