TE is a request header field, and tells the Server that the Client
is willing to support:
* Trailers in the case of chunked transfer-coding (TE: trailers)
* Specific transfer codings (TE: gzip/deflate/identity...)
Transfer-Encoding is a message header (and not an entity header
like Content-Encoding). You need to remove the Transfer-Encodings
(transfer-decode if you want) in the order that they were applied
If you want to access the untransformed message body (containing
the entity).
Hope this helps!
Regards,
Olivier
-----Original Message-----
From: Loïc Minier
Subject: Re: [Ethereal-dev] [HTTP]Desegmentation/Reassembly of HTTP
headers/bodies
Some thought I have that you or the audience could possibly answer:
- anyone heard about the difference between the "TE" header and the
"Transfer-Encoding" header?
- some captures of gzipped/deflated HTTP conversation?
There is a lot of possible enhancements for the packet-http.c
routines. I think Ethereal should provide common lzw-compression
functions or use a third-party lib to deal with all the compressed data
that we can come across, for example in HTTP each "part" of a message
(when parsing a multipart message) could be decompressed and passed to
an appropriate dissector.
--
Loïc Minier <lool@xxxxxxxx>
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev