Bug 104358

Summary: Wrong encoding of filenames containing '@' on upload
Product: [Applications] konqueror Reporter: Johannes Stamminger <Johannes.Stamminger>
Component: khtml formsAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: maksim, rakuco, samuel.brack
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 4.5.4
Sentry Crash Report:
Attachments: testcase

Description Johannes Stamminger 2005-04-22 09:29:34 UTC 
Version:           3.4.0 (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

A webserver allows upload of files. I chose one having a '@' character in it's name using a filechoser dialog. When sending the file a dialog 'Send Confirmation - Koqueror' appears displaying the filename chosen - but the displayed filename is not correct: the '@' char was replaced by %2540 (!).

Having looked to an ASCII table I assume it should have been %40 only, %25 is the replacement for '%' char, it seems as if the filename got encoded recursively/twice in this case ... ?

BTW: encding works fine at least for &, %, ยง, ? but I did not make a complete test ;-).
Comment 1 Johannes Stamminger 2005-04-22 09:52:20 UTC 
I forgot the consequence: no error on uploading but the resulting file is of 0 bytes length afterwards.
Comment 2 Alex Merry 2007-01-06 16:44:18 UTC 
I can reproduce this with KDE 3.5.5.

Test case: upload an 11 byte file called fish@foo to a CMS Made Simple site.  The Send Confirmation dialogue box lists the file as fish%2540foo.  The resulting file on the webserver is fish%40foo, and is empty.

In Firefox, everything works as expected (the complete fish@foo file is uploaded, and has the correct name on the webserver).
Comment 3 Michael Leupold 2008-04-20 14:07:42 UTC 
Created attachment 24441 [details]
testcase

Simple testcase with a file upload form.
Comment 4 Samuel Brack 2011-01-05 00:40:32 UTC 
This seems to be fixed in 4.5.4. Reopen it, if you think that's still a bug.