[Webkit-unassigned] [Bug 10488] New: HTTP parsing confused by HTTP data in body

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=10488

           Summary: HTTP parsing confused by HTTP data in body
           Product: WebKit
           Version: 419.x
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: slamb at slamb.org


In a bugzilla system much like this one, I tried to open an attachment with a
pcap file of an HTTP problem. Safari version 2.0.4 (419.3) exhibited a strange
behavior:

* Safari opened <http://bugzilla.2wire.com/bugzilla/attachment.cgi?id=12275>
(the pcap file). The server (Apache) looks to have sent everything
correctly...application/octet-stream, normal separation between the headers and
body, Content-length: that looks about right, Connection: close and a FIN at
the end.

* Safari opened <http://bugzilla.2wire.com/xslt?PAGE=J01>...the idea of which
must have come from the body of our pcap file!!! Our product uses URLs like
<http://gateway.2wire.net/xslt?PAGE=J01>.

I have a pcap of this happening, which I will attach. I'm curious to see if it
will cause the problem as well...

This happens consistently just by clicking on the attachment link.

Actually, I wonder if this HTTP header is what started the confusion:

    Content-disposition: inline; filename="resin_tcp_reset.enc"

RFC 2606 doesn't mention inline. RFC 2183 does, and it says:

2.1  The Inline Disposition Type

   A bodypart should be marked `inline' if it is intended to be
   displayed automatically upon display of the message.  Inline
   bodyparts should be presented in the order in which they occur,
   subject to the normal semantics of multipart messages.

Not really sure what that means in the context of HTTP.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.