Text display translates "=F1" to "n with a diacrit" in URL, making it invalid



Mail Window Front End
10 years ago
10 years ago


(Reporter: Gina Bull, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: closeme 2008-11-13)



10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2008092417 Firefox/3.0.3
Build Identifier:

RE: Mozilla Thunderbird's processing of links in message text. I copy/pasted the link from the source (View -> Message Source) and from the display area of the application window:

Copied from source of message (this works)

Copied from display (this doesn't work)

The display version translates "=F1" to "n with a diacrit", which renders it invalid as the URL. 

Reproducible: Always

Steps to Reproduce:
1. Try links above (working one was valid as of 10/10/2008)
Actual Results:  
The link in the text display window goes to a "page not found"; the same link when used from the source view works. Compare them to see that "=F1" was translated (but should not have been).

I reported this to Fidelity Investments since it severely impacted the links in their newsletters. Their webmaster may make a report also.

Comment 1

10 years ago
Worksforme over here. 
Please attach a sample of a non-working mail. (Save as file - .eml)

Comment 2

10 years ago
The message may have been encoded in quoted-printable, F1='ñ' in ISO-8859-1.
If this only happens with specific e-mails, it may be malformed by incorrectly encoding the URL (should have been "=3DF1" with q-p for your example).

Comment 3

10 years ago
Gina, could you please respond to comment #1 within two weeks and attach the e-mail in question, or state the "Content-Transfer-Encoding" heading in the context of that link, thus it can be seen if the message is correctly formed?
Whiteboard: closeme 2008-11-13
RESO INCO due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.