Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 7065] HTTP chunked isn't parsed correctly

Date: Fri, 13 Apr 2012 01:21:56 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7065

--- Comment #4 from Sake <sake@xxxxxxxxxx> 2012-04-13 01:21:56 PDT ---
(In reply to comment #3)
> Sorry, now it's attached.

>From RFC 2616:
14.40 Trailer

   The Trailer general field value indicates that the given set of
   header fields is present in the trailer of a message encoded with
   chunked transfer-coding.

       Trailer  = "Trailer" ":" 1#field-name

   An HTTP/1.1 message SHOULD include a Trailer header field in a
   message using chunked transfer-coding with a non-empty trailer. Doing
   so allows the recipient to know which header fields to expect in the
   trailer.

   If no Trailer header field is present, the trailer SHOULD NOT include
   any header fields. See section 3.6.1 for restrictions on the use of
   trailer fields in a "chunked" transfer-coding.

   Message header fields listed in the Trailer header field MUST NOT
   include the following header fields:

      . Transfer-Encoding

      . Content-Length

      . Trailer

This response does not follow the RFC. So wireshark is right in saying the
response is "Malformed".

Do you have a trace with a chunked-encoded body with a trailer that does indeed
follow the RFC?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.