javax.mail truncated url

[ph0ngwh0ng]

Hi!

I use javax.mail to send http mails that include urls. On some mail
clients, including Lotus iNotes, urls contained in the mail are
truncated. For example:

http://www.crappysite.com/index.html?param1=foo&param2=bar

becomes

http://www.crappysite.com/index.html?param1

Encoding in the email is set to "quoted-printable". I tried to set it
to "base64" but it didn't resolve the problem.

Thanks!

Alex

 

[Oliver Wong]

Hi!

I use javax.mail to send http mails that include urls. On some mail
clients, including Lotus iNotes, urls contained in the mail are
truncated. For example:

http://www.crappysite.com/index.html?param1=foo&param2=bar

becomes

http://www.crappysite.com/index.html?param1

Encoding in the email is set to "quoted-printable". I tried to set it
to "base64" but it didn't resolve the problem.

You need to escape the equals character. Quoted Printable and Base 64
are two different formats that coincidentally both treat the '=' character
specially.

- Oliver

 

[ph0ngwh0ng]

And I escape with the " \ " ?

Alex

 

[ph0ngwh0ng]

Ok. Like that:

http://www.crappysite.com/index.html?me&#61dummy...

 

[ph0ngwh0ng]

Argh... I meant the <ampersand>#61..

 

[Roedy Green]

I use javax.mail to send http mails that include urls. On some mail
clients, including Lotus iNotes, urls contained in the mail are
truncated. For example:

http://www.crappysite.com/index.html?param1=foo&param2=bar

becomes

http://www.crappysite.com/index.html?param1

I suppose need to use a hex viewer to see what Lotus Notes likes and
does not like. Once you know that it will be much easier to tell you
how to encode the URLs to keep it happy.

 

[Oliver Wong]

Ok. Like that:
[URL snipped]

Damn... Next time warn me that the link is not work safe. =P I thought
you had posted the code there and wanted me to take a look at it to verify
that it was correct.

but to answer your question, yes, if that works, you can do that, but
that's not the standard way of escaping the '=' character in either
encoding. If you're gonna go with Base64, it's described in RFCs 1421 and
2045.

http://www.ietf.org/rfc/rfc1421.txt

http://www.ietf.org/rfc/rfc2045.txt

- Oliver

 

[Roedy Green]

http://www.crappysite.com/index.html?param1=foo&param2=bar

I would try a simple URLEncode on that prior to any message
level-encoding. It can't hurt.

see http://mindprod.com/jgloss/urlencoded.html