Re: Transparency
2005-09-10 02:19:15
Valdis Klētnieks writes:
Content-Length: was tried and failed already. It totally blows chunks
if you hit a gateway that has to do an 8bit->7bit conversion or other
rewriting (there's still the occasional %-hack usage, or just
canonifying to a FQDN in a From:/To:/cc:/whatever:).
That's not it. Frank meant that the Received should log the body length
as seen at that hop, for easier pinpointing of where munging happened.
Not justified by this problem, IMO, but possibly justified never the
less. There's other munging, there are other bugs, and I at least have
wondered where in the chain it happened.
Could an optional 'length <nonzero>' clause be added to the received
field without restarting the standards clock?
Arnt
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: Transparency, (continued)
- Re: Transparency, Paul Smith
- Re: Transparency, Arnt Gulbrandsen
- Re: Transparency, Alex van den Bogaerdt
- Re: Transparency, Frank Ellermann
- Re: Transparency, Alex van den Bogaerdt
- Re: Transparency, Arnt Gulbrandsen
- Re: Transparency, Frank Ellermann
- Re: Transparency, Valdis . Kletnieks
- Re: Transparency,
Arnt Gulbrandsen <=
- Re: Transparency, John C Klensin
- "More Stuff" in Received header, John Leslie
- Re: "More Stuff" in Received header, Tony Finch
- Re: "More Stuff" in Received header, Frank Ellermann
- Re: Transparency, Frank Ellermann
- "More-stuff" in Received fields (was: Re: Transparency), John C Klensin
- Re: "More-stuff" in Received fields, Frank Ellermann
- Re: "More-stuff" in Received fields, John C Klensin
- Re: "More-stuff" in Received fields, william(at)elan.net
- Changes in CWFS location in 2821bis ABNF (was: Re: Transparency), John C Klensin
|
|
|