[erlang-questions] httpc sending empty te header

Vincent de Phily vincent.dephily@REDACTED
Thu Apr 1 10:16:23 CEST 2010


On Thursday 01 April 2010 08:56:29 Ingela Andin wrote:
> From HTTP rfc:  "If the TE field-value is empty or if no TE field is
> present, the only transfer-coding is "chunked""

Fair enough, that explains why the behaviour is not wrong. But in that case, 
why add the header at all ? You'd save yourself two lines of code, a tiny bit 
of CPU, 5 bytes on the wire, and some confused users.

> > * What's the usefull difference between the "accept-encoding" and the
> > "te" headers ?
> 
> The first one concerns content encoding the second one transfer encoding.

Thanks for these explanations, and sorry for not taking the time to check the 
RFC myself.
-- 
Vincent de Phily
Mobile Devices
+33 (0) 142 119 325
+353 (0) 85 710 6320 

Warning
This message (and any associated files) is intended only for the use of its
intended recipient and may contain information that is confidential, subject
to copyright or constitutes a trade secret. If you are not the intended
recipient you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message, is
strictly prohibited. If you have received this message in error, please
notify us immediately by replying to the message and deleting it from your
computer. Any views or opinions presented are solely those of the author
vincent.dephily@REDACTED and do not necessarily represent those of 
the
company. Although the company has taken reasonable precautions to ensure no
viruses are present in this email, the company cannot accept responsibility
for any loss or damage arising from the use of this email or attachments.


More information about the erlang-questions mailing list