DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16169>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16169

Apache gets currupted chunked response

           Summary: Apache gets currupted chunked response
           Product: Apache httpd-2.0
           Version: HEAD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Core
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


When mod_dav and mod_dav_fs modules are used and the response is relatively 
big Apache corrupts it, e.g. a lot of zeros, some symbols < 0x20, etc. in the 
xml output.

Few details. 
PROPFIND method was used against a big directory (> 400 files), following 
request headers were sent:

PROPFIND / HTTP/1.1
Content-Type: text/xml; charset="utf-8"
Content-Length: 94
Host: localhost:801
Accept: text/html, */*'
User-Agent: Mozilla/3.0 (compatible; DD Library)
Authorization: Basic xxxxxxx..removed...
Depth: 1

Following request body:

<?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:">
<D:allprop/>
</D:propfind>
^^^ no EOL at the end. Only 94 bytes.

Following responce headers were given:

HTTP/1.1 207 Multi-Status
Date: Thu, 16 Jan 2003 14:32:03 GMT
Server: Apache/2.1.0-dev (Win32) DAV/2
Transfer-Encoding: chunked
Content-Type: text/xml; charset="utf-8"

responce body is 386kb - too big to list it here.

Some excerpts:
at the beginning everything ok. 1st chunk:
1f45
<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:">
<D:response xmlns:lp1="DAV:" xmlns:lp2="http://apache.org/dav/props/";>
<D:href>/function.ftruncate.html</D:href>
....
2nd chunk:
1f44
<D:propstat>
<D:prop>
<lp1:creationdate>2003-01-16T14:04:47Z</lp1:creationdate>
....
3rd chunk:
1fb1
<lp1:getetag>"90426340-971-641d2b80"</lp1:getetag>
<lp1:resourcetype/>
<D:supportedlock>
....
4th chunk:
1f59
<D:lockdiscovery/>
<D:getcontenttype>text/html</D:getcontenttype>
</D:prop>
....
5th chunk:
1f54
</D:href>
<D:propstat>
<D:prop>
.....
corrpution: from 0x9DBE up to 0xBD77 all are zeros then 6th chunk.

Sometimes corrputed block is big, sometimes is very small and contains wrong 
symbols (<0x20 and >0x7f). Sometimes it occurs in one offset, sometimes in a 
bit different. Always it occurs in region of ~10% of the stream.

Please contact me at my e-mail and I'll provide you all you need to reproduce 
the problem. I tried both Jan16th cvs snapshot and official 2.0.43. Both gets 
the trouble. OS - Windows XP (w/o SP1).

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to