181598 - Problem handling "<url:"

Status: RESOLVED WORKSFORME

(MailNews Core :: MIME, defect)

Description

[Frederic Bezies]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021123
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021123

I cannot find a duplicate of this bug, and I don't really know where to post it :-/

When I click on a link like "<url:www.some website address.com>" I have an error
box saying "Url is not a registered protocol".

Reproducible: Always

Steps to Reproduce:
1.Open a news post with an "<url:" URL address, for example :
"<url:http://www.outertech.com/>"
2.Click on it to open the website in mozilla browser.


Actual Results:  
Getting a dialog box saying "Url is not a registered protocol"

Expected Results:  
Opening the site in mozilla browser.

Here is the error message I've got in JavaScript Console :

"Error: uncaught exception: [Exception... "Component returned failure code:
0x804b0012 [nsIWebNavigation.loadURI]"  nsresult: "0x804b0012 (<unknown>)" 
location: "JS frame ::
chrome://global/content/bindings/browser.xml#browser.loadURIWithFlags() ::
loadURIWithFlags :: line 5"  data: no]"

I am using a 2 hours old CVS based build - WinXP-Sp1.

Comment 1

[Thomas Holaday]

I have not been able to find any examples of the given syntax <url:http:// ...
[note there is no space between the "url:" and the "http://" in the first dozen
hits I get with a google search of groups.  There are many examples of "url:
http:// ..." [with a space between the "url:" and the "http://" and Mozilla
handles them properly, that is, by opening the web page.  I believe the given
syntax is an error, and that Mozilla is correct in reporting that URL is not a
protocol.

Comment 2

[Frederic Bezies]

Here is the page where you can find on google the post from which I report this bug.

http://groups.google.com/groups?dq=&hl=fr&lr=&ie=UTF-8&selm=alqstu4gg47ujqliu38f7rfu599huo7u1q%404ax.com

Sorry for url length.

When I look at the page, only the "http://" part is highlighted.

In mailnews, all is hightlighted.

Is this a clue for this bug ?!

Comment 3

[Frederic Bezies]

Here is a test case for this bug.

Send this message in a test newsgroup :

"
<url:http://www.mozilla.org/>

<URL:http://www.mozilla.org/>

"

First line -> bug.

Second line -> browser is launched and loading website.

I "verified" the bug with a 4 hours old CVS based build - WinXP.

Comment 4

[timeless]

benb

Comment 5

[Ben Bucksch (:BenB)]

ah, comment 3 says it.

The old standard (RFC1738) says "<URL:", not "<url:". Newer versions of the
standard (RFC2396) don't mentioned "<URL:" at all anymore. The recognition of
"<URL:" was added as support for that legacy standard.

"<url:http:bla>" looks like the url scheme "url".

Not sure what to do. I could mark invalid, saying "use correct case".

Comment 6

[Frederic Bezies]

Why not supporting both of them ? This should be a bug from some news software,
like ForteAgent or Gravity ?

Well, you should see :-)

Comment 7

[Jari Laaksonen]

Any progress on this?

Just for the reference, Netscape 4.8 Messenger parses all these correctly, i.e.
the actual URL part is shown as link:

<url:http://www.mozilla.org/>
<url: http://www.mozilla.org/>
<URL:http://www.mozilla.org/>
<URL: http://www.mozilla.org/>

Comment 8

[Mike Cowperthwaite]

It's not clear to me how much of this bug is about (fully?) linkifying a 
plain-text string   <url:http://mozilla.org>   and how much is about that link 
failing to operate.  I see the lower-case "url" form get properly linkified 
for everything after the "url:" -- and clicking that link opens the page as expected.  Is there anything else needed here?

Comment 9

[Mike Cowperthwaite]

No response  => WFM