278715 - incorrectly parses urls containing curly braces, { }

Status: RESOLVED FIXED

(Thunderbird :: Mail Window Front End, defect)

Description

[Daniel R. Ehrlich]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When I view a message with urls containg open and close curly braces the parser
always thinks the url stops at the closing curly brace.

I.E.

http://cbs.marketwatch.com/p.asp?guid={39C6AF9D-A877-4A33-85A5-6F94AD56A4D0}&d=bnb

will only send

http://cbs.marketwatch.com/p.asp?guid={39C6AF9D-A877-4A33-85A5-6F94AD56A4D0}

to the browser when I click on the url.

-- Dan Ehrlich


Reproducible: Always

Steps to Reproduce:
1. create a mail message containg the offending url
2. 
3.

Actual Results:  
incomplete parsing of the url

Expected Results:  
correctly parse the url

Comment 1

[Mike Capp]

Hmm. The full URL is parsed "correctly" by FF (I don't have Tbird) but I'm
wondering whether that isn't undefined behaviour - as I understand it, curly
braces shouldn't make it into URLs unescaped.

From http://www.faqs.org/rfcs/rfc1738.html (Uniform Resource Locators)

"Other characters are unsafe because gateways and other transport agents are
known to sometimes modify such characters. These characters are "{", "}", "|",
"\", "^", "~", "[", "]", and "`". All unsafe characters must always be encoded
within a URL."

Note the "must". Shouldn't '{' and '}' be escaped in the same way that spaces are?

Comment 2

[Daniel R. Ehrlich]

I have informed the offending author of the error of their ways.  Feel free to
close this bug.  And sorry to have bother you.