221953 - error 404 in one frame appears when some of the entries of a flash player application are chosen

Status: RESOLVED EXPIRED

(Core Graveyard :: Plug-ins, defect)

Description

[Andy]

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

Either click on
Leistungen->Komplett Kits
or
Gästebuch
in the left frame.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Actual Results:  
error 404: Datei nicht gefunden!
Das angegebene Dokument konnte auf diesem Server leider nicht gefunden werden.

and

Fehler
404: Nicht gefunden (Not Found)
[....]

Expected Results:  
A table

or appropriately

a guestbook should appear.


Shockwave Flash
    File name: NPSWF32.dll
    Shockwave Flash 7.0 r14

With IE 6.0 (Flash version 6.0) it shows up correctly.

Comment 1

[Andreas Kunz]

Sniffing my network while trying this I found that Moz and IE sent different
requests for those pages:

Gästebuch:
IE:  GET http://gb2003.de/a/rueddel.html HTTP/1.1
Moz: GET http://gb2003.de/a/rueddel.html%20 HTTP/1.1

Komplett Kits:
IE:  GET http://www.rueddel-motorsport.de/Komplett-Kits/komplett-kits.html HTTP/1.1
Moz: GET http://www.rueddel-motorsport.de/Komplett-Kits%5Ckomplett-kits.html
HTTP/1.1

But I'm not sure if this is caused by a badly programmed Flash thingie or if
Mozilla screwed this up.

Comment 2

[Andy]

Andreas Kunz wrote (2004-01-21 19:03):
[...]
> Moz: GET http://gb2003.de/a/rueddel.html%20 HTTP/1.1

%20 is a translated blank

> IE:  GET http://www.rueddel-motorsport.de/Komplett-Kits/komplett-kits.html 
> Moz: GET http://www.rueddel-motorsport.de/Komplett-Kits%5Ckomplett-kits.html

%5C is a backslash and the funny thing is that if I enter it as
http://www.rueddel-motorsport.de/Komplett-Kits\komplett-kits.html
IE leaves it unchanged (in the address bar) and this link then works,
Mozilla however translates it into the link given above (with %5C) and this then
doesn't work.

> But I'm not sure if this is caused by a badly programmed Flash thingie or if
> Mozilla screwed this up.

Perhaps there is some blank space and backslash in his code and IE drops the
space and translates the backslash to a normal slash.

Comment 3

[Andy]

So why not to create some options like:

Enable dirty IE compatibility hacks:
 [ ] Delete trailing whitespace from URLs before handing them over to plug-ins
 [ ] Translate backslashes in "path part" of the URL into slashes (only in path
part, since I have seen some translated backslashes while searching on google,
e.g.http://www.climate.weatheroffice.ec.gc.ca/climateData/canada_e.html?Etimeframe=%21%23%40%20%20%0A&EProv=%229%5B%5C%20%0A&EStationID=%25%21M%5BP%21%2A%28%20%0A&EYear=%24%23%3D%3FY%23%40%20%20%0A&EMonth=%21%21%40%20%20%0A&EDay=%22%23%3D%3C%20%0A
)

These options should IMHO not be hidden somewhere deep in options menu, but
be directly accessable through an additional icon (like the one for cookies).
(The problematic URLs could also be detected and then this icon could change
somehow.)

Any comments?

Comment 4

[Noam Tamim]

Isn't this a dupe of Bug 122270?

Comment 5

[Andy]

> Isn't this a dupe of Bug 122270?

Only partially, bug 122270 is about backslashes, this bug is about different
handling of backslashes and _blanks_ in IE.

(The component specified above is probably wrong, the component should be the
part of mozilla that passes the urls to the plug-ins).

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.