184841 - iframe src="c:\" produces "c is not a registered protocol"

Status: RESOLVED DUPLICATE of bug 196120

(Core :: DOM: Navigation, defect)

Description

[Henrik Gemal]

if you go to:
http://www.gulli.com/tools/anoncheck.html
you get an alert:
"c is not a registered protocol"

20021210 on WinXP

Comment 1

[Henrik Gemal]

it's the:
<iframe src="c:\"></iframe>
that produces the alert

Comment 2

[Henrik Gemal]

Attachment: test case

Comment 3

[benc]

We corrected the handling of relative URLs, c: is recognized as a protocol handler.

You need to correctly escape the ":", or you might find that "c|" works.

Comment 4

[Doug Turner (:dougt)]

src="c:\" is not a valid URL.  If they wanted to load the contents of the c:\
 directory, they should try "file://c:" or something (ignoring the fact that
this is also invalid when loaded from a remote site).

Comment 5

[Henrik Gemal]

for normal users producing an alert saying "c is not a registered protocol" is
really really weird. The error says nothing about what's going on and where and
how to correct this.

I suggest we remove such a alert and perhaps move it to the javascript console
as an error or something.

At least only show this error if you're running a debug build.

Comment 6

[Doug Turner (:dougt)]

sure, we can do that.  get someone from the front end to agree how unrecognized
protocols should be handled from iframes vs. the url bar.  

Comment 7

[Boris Zbarsky [:bzbarsky]]

We _have_ to show this error if the user clicks on <a href="c:\">.  Simply doing
nothing is not acceptable there.

This is simply a duplicate of the bug on using error pages instead of alerts --
if we showed a nice error page in the iframe it would all be fine.

*** This bug has been marked as a duplicate of 28586 ***

*** This bug has been marked as a duplicate of 28586 ***

Comment 8

[Andreas Otte]

I think the current error message is correct and should be left as it is. It
exactly says what is going on. c is interpreted as protocol, this might give a
hint to the user/designer that he/she missed the file:/// prefix. After fixing
this he/she will of course get a 404 because of the usage of \ instead of /. 

Using an error page instead of the alert may be acceptable as long as the
message stays the way it is.

Comment 9

[Boris Zbarsky [:bzbarsky]]

Of course.  The error page will likely say something like:

'Unable to load "c:\" because "c" is an unknown protocol'....

Comment 10

[benc]

REOPEN: duped to wrong bug.

Comment 11

[benc]

iframes will not error anymore.

*** This bug has been marked as a duplicate of 196120 ***