tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Preißer <kpreis...@apache.org>
Subject RE: [OT] RE: Baked-in context paths
Date Mon, 18 Nov 2013 14:35:41 GMT
Hi,

> -----Original Message-----
> From: Konstantin Preißer [mailto:kpreisser@apache.org]
> Sent: Wednesday, November 13, 2013 6:14 PM
> To: 'Tomcat Users List'
> Subject: RE: [OT] RE: Baked-in context paths
> 
> Hi Jeffrey,
> 
> > -----Original Message-----
> > From: Jeffrey Janner [mailto:Jeffrey.Janner@PolyDyne.com]
> > Sent: Wednesday, November 13, 2013 5:14 PM
> > To: 'Tomcat Users List'
> > Subject: RE: [OT] RE: Baked-in context paths
> >
> > The thing is, the garbage characters at the end don't exist in the email I see
> as I type.
> > They are either hidden in the editor or getting added by Outlook (2007) or
> Exchange (2010).
> 
> They are "added" by the list mailer of this mailing list, not by your mail client -
> it is the the following lines:
> 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> 
> The problem here is that your client sent the mail content as Base64, and the
> list mailer adds these lines as a separate Base64 block which (in my opinion) is
> probably wrong - it produces invalid Base64 data, which causes such junk
> characters on some mailing clients (and an empty mail on my client).
> 
> This also happens with some other mails like the one from Buildbot on the
> Dev list - these are are also sent as Base64 which then show blank for me.

Should I report this problem somewhere, e.g. on the Apache Infra JIRA?

Note that this problem does not always appear - I think it happens only if (original_message_length_in_bytes
% 3 != 0), because then the last 4 characters sequence does not represent 3 bytes, but only
1 or 2, and therefore has some "=" characters at the end. However, in the other case, the
last 4 characters represent full 3 bytes, so another Base64 block can be added without corrupting
the data.

E.g., if you look at this mail from Buildbot [1], you can see that the bottom contains the
"To unsubscribe..." text added by the mailing list. This mail displayed correctly in my mail
client. If you look at the raw message, you can see that the first Base64 block represents
429 bytes, and as 429 % 3 == 0 there isn't a problem.

If you look at this mail from Buildbot [2], then the bottom doesn't contain the "To unsubscribe"
lines. In the raw message, you can see the first Base64 block represents 403 bytes (403 %
3 == 1), so it contains "==" at the end, and the added Base64 block makes the Base64 invalid.
This email displayed blank in my client.


[1] http://mail-archives.apache.org/mod_mbox/tomcat-dev/201311.mbox/%3C20131118012335.AB0A6C04A4%40aegis.apache.org%3E
[2] http://mail-archives.apache.org/mod_mbox/tomcat-dev/201311.mbox/%3C20131118032322.48526C04A4%40aegis.apache.org%3E


Regards,
Konstantin Preißer


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message