213628 - Mozilla uploads wrong / empty file / does not upload file when filename or pathname includes no-break space ASCII character 160 ( )

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Aaron Kaluszka]

When trying to submit an attachment to a bug, Bugzilla kept telling me that the
file I submitted was empty.  I finally narrowed it down to the pathname.  The
file was in "My Documents" directory, and my profile is named "Aaron. " since my
computer name is the no-break space, ASCII character 160.  Upon futher testing,
I found that the same thing would happen if this character was anywhere in the
path or filename.  I tried other extended ASCII characters, but they worked.  It
seems like Mozilla is escaping this character as a regular space and is trying
to upload a file from a place that doesn't exist resulting in dataloss.  To test
this theory, I tried creating a file with the same name except with a regular
space in the name and then attempted to upload the file with the no-break space.
 Mozilla appeared to upload the file with the regular space instead.  IE works
fine.  Firebird 20030714/WinXP.

Comment 1

[Hadrien Nilsson]

Bug confirmed with Firebird 0.7+ 20031106
I tried to upload a file which filename containes à no-break space. I got an
error when uploading.

I submitted a patch for bug 218277 which also corrects this bug : I did the same
test with my own Mozilla modified version, and the upload worked fine.

bug 195946 is also concerned.

Comment 2

[Robin Monks]

*** Bug 278897 has been marked as a duplicate of this bug. ***

Comment 3

[Peter Flynn (Oracle)]

The same result seems to occur with ASCII 255 in the file name--a 0-length file
is sent.  But looking at bug #218277 it seems that the cause of this must be
coming from completely different code than the ASCII 160 problem.

Comment 4

[Adam Guthrie]

*** Bug 310476 has been marked as a duplicate of this bug. ***

Comment 5

[Paul Borokhov (lensovet)]

hmm, this bug is marked "critical", dataloss, and affects all mozilla products. why hasn't it been fixed? a patch to fix this was available over two years ago.

Comment 6

[Boris Zbarsky [:bzbarsky]]

This should be fixed on trunk now that bug 218277 has been checked in.  Reporter, can you verify (with a Minefield or trunk Seamonkey build)?

Comment 7

[Paul Borokhov (lensovet)]

works fine with Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20061121 Minefield/3.0a1. apologies for the bugspam.