You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Leo Donahue - OETX <Le...@mail.maricopa.gov> on 2013/11/06 23:28:34 UTC
[OT] RE: Baked-in context paths
>-----Original Message-----
>From: Leo Donahue - OETX [mailto:LeoDonahue@mail.maricopa.gov]
>Subject: RE: Baked-in context paths
>
>
>B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
>KKKKKKCB�� [��X��ܚX�KK[XZ[
>
>� \�\��][��X��ܚX�P �X�]
>�\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
>
>� \�\��Z[ �X�]
>�\X�K�ܙ�B�
I don't know why my email client keeps adding this junk. There isn't even a carriage return after this line. Sorry for the wasted bits.
RE: [OT] RE: Baked-in context paths
Posted by Konstantin Preißer <kp...@apache.org>.
Hi Christopher,
> -----Original Message-----
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Sent: Monday, November 18, 2013 7:28 PM
> To: Tomcat Users List
> Subject: Re: [OT] RE: Baked-in context paths
<snip>
> > Should I report this problem somewhere, e.g. on the Apache Infra
> > JIRA?
<snip>
> Interesting observation. I think you should report it to infra@
>
> - -chris
Ok, thanks. I have created an issue here (hope this was the right place): https://issues.apache.org/jira/browse/INFRA-7052
Regards,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] RE: Baked-in context paths
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Konstantin,
On 11/18/13, 9:35 AM, Konstantin Preißer wrote:
> 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
Interesting observation. I think you should report it to infra@
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJSilwZAAoJEBzwKT+lPKRYsP4QAMmYqPQXLx/r979z3xkfTZLL
hnYZTW2oYayEBY8Ooip0/Hs8qoJFeKo5AcRU9DrNM/dDa7H+lsUEeP3/6REFhdBr
7xTNJu5mVK0I0A/UK22HVc3UIyTKwRW9viA4n28Dk9Mn5znvXX9tGL0YgfPdfo+5
KhPGll0p5W15cz7TPC4rIxOXk6u5519gSOiJolL4xCEWNLbrwvIjtjbEHxXl06xt
CZ9PE4Y7G1EBhyCMGKcfW3AsKoXI23omv8w4lEfXq2Y3VCoLr/IRZSIX7RpONC5i
Rrf+TabcIMwjk+R0E4FyqBXMVYsf/bI57ZPf/hYq5ioywiMW4QkWnrjoCPlx5rme
fSQ/U7jA8lFZ8D6sCeopqHZTTFP2b9oerT4cKTLrRU4hXYzGKv6BFKSkl7haLh7s
qBUeZGjw3o3t+ylkwFpn4rwPNqooo+E6I2IkNWhglg+peVFac4lfKpxCG4i1snct
vy0efGrTy8Tqy5thh5tNnqzRzIxzDzoWQNHWu5MYEMJaWY9i8zA/786PhQsrOlDE
c1SE37uKhVIoL97tFjmtK7+M3jJuJCFCwFJgq7QehmVCUm9wg/UvY+zYFcMPTI2C
jEi101NYSgT4ECw/Ix7K8AAxpd813xIBLfOTIWVJISMHBysUxYWTUA/a0f3D7QFb
rnPSDU0H7LY2jZVLiL0d
=sQjX
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: [OT] RE: Baked-in context paths
Posted by Konstantin Preißer <kp...@apache.org>.
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
RE: [OT] RE: Baked-in context paths
Posted by Konstantin Preißer <kp...@apache.org>.
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.
Regards,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: [OT] RE: Baked-in context paths
Posted by Jeffrey Janner <Je...@PolyDyne.com>.
> -----Original Message-----
> From: Konstantin Preißer [mailto:kpreisser@apache.org]
> Sent: Wednesday, November 13, 2013 7:17 AM
> To: 'Tomcat Users List'
> Subject: RE: [OT] RE: Baked-in context paths
>
> > -----Original Message-----
> > From: Konstantin Preißer [mailto:kpreisser@apache.org]
> > Sent: Tuesday, November 12, 2013 8:09 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: Tuesday, November 12, 2013 4:22 PM
> > > To: 'Tomcat Users List'
> > > Subject: RE: [OT] RE: Baked-in context paths
> > >
> >
> > I'm also using Outlook, but for me it only shows an empty email here.
> >
> > If I open the mail in the Apache Mail-Archives (http://mail-
> > archives.apache.org/mod_mbox/tomcat-
> > users/201311.mbox/%3C7215BA462D00D343B2837F9113F0131F0181A0E612%
> > 40POSTOFFICE02.polydyne.com%3E), then I can see the text, but it does
> > not show the three "To unsubscribe ..." text added by the list mailer
> > at the bottom.
> >
> > If I view the raw message, I can see two Base64 encoded blocks. The
> > first block contains the email text, the second one contains the
> three
> > lines added by the mailer.
> >
> > I would guess that your Outlook tries to decode the two blocks as one
> > block (which fails), so latter produces the junk which you can see
> > (and probably because of this I get an empty mail).
> >
> > However, I don't have much knowledge about email standards or Outlook
> > to know what exactly is wrong here.
>
> BTW,
>
> If I take the two Base64 blocks of your message, remove the first "="
> sign from the end of the first block, remove all whitespaces and decode
> it as one block, then I get the same "junk" characters end the end of
> the message text.
> I also opened the mail in another mail client (some web mail UI from my
> mailbox provider) and it also shows the message text with some junk
> characters at the end.
>
> My guess would be that the problem here is not Outlook (however one
> could question why it is encoding the sent message content as Base64 in
> the first place, instead of something like quoted-printable), but the
> list mailer, as instead of just adding another Base64 block which
> produces invalid data, it probably should decode the first block, add
> the "To unsubscribe..." text, and re-encode it, so that it is one valid
> Base64 block.
>
> However, because in this case the message content is invalid Base64, it
> depends on the client how it tries to work-around it (so in my case, it
> shows only an empty message).
>
>
> Regards,
> Konstantin Preißer
>
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).
RE: [OT] RE: Baked-in context paths
Posted by Konstantin Preißer <kp...@apache.org>.
> -----Original Message-----
> From: Konstantin Preißer [mailto:kpreisser@apache.org]
> Sent: Tuesday, November 12, 2013 8:09 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: Tuesday, November 12, 2013 4:22 PM
> > To: 'Tomcat Users List'
> > Subject: RE: [OT] RE: Baked-in context paths
> >
>
> I'm also using Outlook, but for me it only shows an empty email here.
>
> If I open the mail in the Apache Mail-Archives (http://mail-
> archives.apache.org/mod_mbox/tomcat-
> users/201311.mbox/%3C7215BA462D00D343B2837F9113F0131F0181A0E612%
> 40POSTOFFICE02.polydyne.com%3E), then I can see the text, but it does not
> show the three "To unsubscribe ..." text added by the list mailer at the
> bottom.
>
> If I view the raw message, I can see two Base64 encoded blocks. The first
> block contains the email text, the second one contains the three lines added
> by the mailer.
>
> I would guess that your Outlook tries to decode the two blocks as one block
> (which fails), so latter produces the junk which you can see (and probably
> because of this I get an empty mail).
>
> However, I don't have much knowledge about email standards or Outlook to
> know what exactly is wrong here.
BTW,
If I take the two Base64 blocks of your message, remove the first "=" sign from the end of the first block, remove all whitespaces and decode it as one block, then I get the same "junk" characters end the end of the message text.
I also opened the mail in another mail client (some web mail UI from my mailbox provider) and it also shows the message text with some junk characters at the end.
My guess would be that the problem here is not Outlook (however one could question why it is encoding the sent message content as Base64 in the first place, instead of something like quoted-printable), but the list mailer, as instead of just adding another Base64 block which produces invalid data, it probably should decode the first block, add the "To unsubscribe..." text, and re-encode it, so that it is one valid Base64 block.
However, because in this case the message content is invalid Base64, it depends on the client how it tries to work-around it (so in my case, it shows only an empty message).
Regards,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: [OT] RE: Baked-in context paths
Posted by Konstantin Preißer <kp...@apache.org>.
Hi Jeffrey,
> -----Original Message-----
> From: Jeffrey Janner [mailto:Jeffrey.Janner@PolyDyne.com]
> Sent: Tuesday, November 12, 2013 4:22 PM
> To: 'Tomcat Users List'
> Subject: RE: [OT] RE: Baked-in context paths
>
I'm also using Outlook, but for me it only shows an empty email here.
If I open the mail in the Apache Mail-Archives (http://mail-archives.apache.org/mod_mbox/tomcat-users/201311.mbox/%3C7215BA462D00D343B2837F9113F0131F0181A0E612%40POSTOFFICE02.polydyne.com%3E), then I can see the text, but it does not show the three "To unsubscribe ..." text added by the list mailer at the bottom.
If I view the raw message, I can see two Base64 encoded blocks. The first block contains the email text, the second one contains the three lines added by the mailer.
I would guess that your Outlook tries to decode the two blocks as one block (which fails), so latter produces the junk which you can see (and probably because of this I get an empty mail).
However, I don't have much knowledge about email standards or Outlook to know what exactly is wrong here.
Regards,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: [OT] RE: Baked-in context paths
Posted by Jeffrey Janner <Je...@PolyDyne.com>.
> -----Original Message-----
> From: Jeffrey Janner [mailto:Jeffrey.Janner@PolyDyne.com]
> Sent: Monday, November 11, 2013 9:55 AM
> To: 'Tomcat Users List'
> Subject: RE: [OT] RE: Baked-in context paths
>
> > -----Original Message-----
> > From: Christopher Schultz [mailto:chris@christopherschultz.net]
> > Sent: Thursday, November 07, 2013 10:07 AM
> > To: Tomcat Users List
> > Subject: Re: [OT] RE: Baked-in context paths
> >
> >
> > Jeff,
> >
> > On 11/7/13, 10:17 AM, Jeffrey Janner wrote:
> > >> -----Original Message----- From: Leo Donahue - OETX
> > >> [mailto:LeoDonahue@mail.maricopa.gov] Sent: Wednesday, November
> 06,
> > >> 2013 4:29 PM To: Tomcat Users List Subject: [OT] RE: Baked-in
> > context
> > >> paths
> > >>
> > >>> -----Original Message----- From: Leo Donahue - OETX
> > >>> [mailto:LeoDonahue@mail.maricopa.gov] Subject: RE: Baked-in
> > >>> context paths
> > >>>
[...snip...]
> > >> I don't know why my email client keeps adding this junk. There
> > isn't
> > >> even a carriage return after this line. Sorry for the wasted
> bits.
> > >
> > > You must be using Outlook. My Outlook tends to do that every time I
> > > reply to one of Chris' PGP-signed messages. The trick is to make
> > > sure you remove all the PGP signature and all the header bits
> > > associated with it.
> >
> > :(
> >
> > I didn't know that was happening. I used to use PGP/MIME but
> evidently
> > that made my messages invisible (i.e. no-content) for some people
> with
> > ... less capable email readers. So I switched to in-message
> signatures
> > which seemed to be a bit more compatible.
> >
> > Apologies for the inconvenience.
> >
> > - -chris
>
> No real problem Chris. I normally delete everything at the end of a
> message that's not relevant to the message. It's just that I sometimes
> forget to remove the "BEGIN PGP MESSAGE" and hash line at the top of
> the message, and so for some reason Outlook still puts in a bunch of
> junk at the end.
> Not really your fault. If only MS would support industry standards
> better, we'd all be better off. (I also can't set it to not top-post
> replies.) B
> KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB
> [ X ܚX KK[XZ[
>
> \ \ ][ X ܚX P X ]
> \X K ܙ B ܈Y][ۘ[ [X[ K[XZ[
>
> \ \ Z[ X ]
> \X K ܙ B
Ack! Ack! Spfft! Spfft! Ack!
F-in Microsoft!
RE: [OT] RE: Baked-in context paths
Posted by Jeffrey Janner <Je...@PolyDyne.com>.
> -----Original Message-----
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Sent: Thursday, November 07, 2013 10:07 AM
> To: Tomcat Users List
> Subject: Re: [OT] RE: Baked-in context paths
>
>
> Jeff,
>
> On 11/7/13, 10:17 AM, Jeffrey Janner wrote:
> >> -----Original Message----- From: Leo Donahue - OETX
> >> [mailto:LeoDonahue@mail.maricopa.gov] Sent: Wednesday, November 06,
> >> 2013 4:29 PM To: Tomcat Users List Subject: [OT] RE: Baked-in
> context
> >> paths
> >>
> >>> -----Original Message----- From: Leo Donahue - OETX
> >>> [mailto:LeoDonahue@mail.maricopa.gov] Subject: RE: Baked-in context
> >>> paths
> >>>
> >>>
> >>> B KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
> >>>
> >>>
> KKKKKKCB [ X ܚX KK[XZ[
> >>>
> >>> \ \ ][ X ܚX P X ]
> >>> \X K ܙ B ܈Y][ۘ[ [X[ K[XZ[
> >>>
> >>> \ \ Z[ X ] \X K ܙ B
> >>
> >> I don't know why my email client keeps adding this junk. There
> isn't
> >> even a carriage return after this line. Sorry for the wasted bits.
> >
> > You must be using Outlook. My Outlook tends to do that every time I
> > reply to one of Chris' PGP-signed messages. The trick is to make sure
> > you remove all the PGP signature and all the header bits associated
> > with it.
>
> :(
>
> I didn't know that was happening. I used to use PGP/MIME but evidently
> that made my messages invisible (i.e. no-content) for some people with
> ... less capable email readers. So I switched to in-message signatures
> which seemed to be a bit more compatible.
>
> Apologies for the inconvenience.
>
> - -chris
No real problem Chris. I normally delete everything at the end of a message that's not relevant to the message. It's just that I sometimes forget to remove the "BEGIN PGP MESSAGE" and hash line at the top of the message, and so for some reason Outlook still puts in a bunch of junk at the end.
Not really your fault. If only MS would support industry standards better, we'd all be better off. (I also can't set it to not top-post replies.)
Re: [OT] RE: Baked-in context paths
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Jeff,
On 11/7/13, 10:17 AM, Jeffrey Janner wrote:
>> -----Original Message----- From: Leo Donahue - OETX
>> [mailto:LeoDonahue@mail.maricopa.gov] Sent: Wednesday, November
>> 06, 2013 4:29 PM To: Tomcat Users List Subject: [OT] RE: Baked-in
>> context paths
>>
>>> -----Original Message----- From: Leo Donahue - OETX
>>> [mailto:LeoDonahue@mail.maricopa.gov] Subject: RE: Baked-in
>>> context paths
>>>
>>>
>>> B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
>>>
>>>
KKKKKKCB�� [��X��ܚX�KK[XZ[
>>>
>>> � \�\��][��X��ܚX�P �X�]
>>> �\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
>>>
>>> � \�\��Z[ �X�] �\X�K�ܙ�B�
>>
>> I don't know why my email client keeps adding this junk. There
>> isn't even a carriage return after this line. Sorry for the
>> wasted bits.
>
> You must be using Outlook. My Outlook tends to do that every time I
> reply to one of Chris' PGP-signed messages. The trick is to make
> sure you remove all the PGP signature and all the header bits
> associated with it.
:(
I didn't know that was happening. I used to use PGP/MIME but evidently
that made my messages invisible (i.e. no-content) for some people with
... less capable email readers. So I switched to in-message signatures
which seemed to be a bit more compatible.
Apologies for the inconvenience.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJSe7qpAAoJEBzwKT+lPKRYpEgP/0OJoh8d2QgTC82MA0ioaKlM
Q4F2kfpFcfQLul/L9gBGDcuxSarWm3dd+A6ieETnm+QLeiq/mGvbJ0egTUZHor2T
eoMcqQkxlEGBMuyMGFG2zHCdK5uVDcVbJpvBjQ6UXOvAgWHBDmEpa/N5CB4XejWy
MnV/ih4xx7Ge9lFTmXcF9g7V12fq2ZV3aVs7n9qbsj9CG7TENPin1A02D720bo7w
u3YaQeYQtcPaJHObBPQ6T6CbGVxHjw48qks614lBAYYQveyV0qX7ws+jUFaGAwId
erLUo3teSOjq8Bt0ztcusp6xHFjf6ZiwU5xYy8Zie2wvkT0xVX8UNEfGgLSKBhqq
u+Ct8d+tLwJG+K/cDU09hRLIvyggITPlGtvF/+vDe9dYKDFDqbJ5PD5YUZlCPzx6
qmLJrTASJf5BH4OVQEHuheT9RppJ/O9lw7UX5ohLo8CpB3Sg2/h8oIpVPWtuEpHS
SWTw0kUDovbnG/XILZHY/EVHm/phgwnLTmJgKhMFruqyf+YUkzZbj6hbopBwDzJm
HCigxI/3+u5/4iIO54CwI3K/k3tEUydsK4/ZOeer0rtVJBkkYxpNqJgmu87EUl59
EMzAReb242zoiwH/AJ1Kdk+j21JJYbvxUJgvdpg0ZNAQM3grQo7LSeaFeb2w4T7n
N6Rw7yvAPKMUsEA0xdJ+
=04Vr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: [OT] RE: Baked-in context paths
Posted by Jeffrey Janner <Je...@PolyDyne.com>.
> -----Original Message-----
> From: Leo Donahue - OETX [mailto:LeoDonahue@mail.maricopa.gov]
> Sent: Wednesday, November 06, 2013 4:29 PM
> To: Tomcat Users List
> Subject: [OT] RE: Baked-in context paths
>
> >-----Original Message-----
> >From: Leo Donahue - OETX [mailto:LeoDonahue@mail.maricopa.gov]
> >Subject: RE: Baked-in context paths
> >
> >
> >B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
> >KKKKKKCB�� [��X��ܚX�KK[XZ[
> >
> >� \�\��][��X��ܚX�P �X�]
> >�\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
> >
> >� \�\��Z[ �X�]
> >�\X�K�ܙ�B�
>
> I don't know why my email client keeps adding this junk. There isn't
> even a carriage return after this line. Sorry for the wasted bits.
You must be using Outlook.
My Outlook tends to do that every time I reply to one of Chris' PGP-signed messages.
The trick is to make sure you remove all the PGP signature and all the header bits associated with it.
Jeff