![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Firefox changes "(" to "%28" in download filenames. IE does not. How to fix?
When I download a file from a web site: Example ----- file (test) number1.pdf Using IE, the downloaded file is named --------------------- file (test) number1.pdf Using Firefox (36.0.1) the downloaded file is named --- file %28test%29 number1.pdf
Is there any way to configure FF to retain literal file names when downloading? I understand the historical reasons behind substitution, but am surprised I can't configure this.
Todas las respuestas (2)
I think that this should work normally. You would only get the parentheses and other reserved characters escaped if you copy as link from the location/address bar. This shouldn't happen when saving a file. How are these files send?
You can use the Live Http Headers to check this:
Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.
- Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
- Do NOT click the Reset button on the Safe Mode start window
Okay, I'm starting to understand the problem a little.
Starting/running in safe mode had no affect on the problem. Bit I figured out that what I was copying/downloading WAS indeed a link to a file. If I first opened a file (a PDF) it would show its name with %28 (etc). But, if in Adobe Reader I did a 'Save As', the parentheses in the name return.
So, I guess my real question at this point now refers to avoiding the substitution when working with links. Maybe this can't be fixed. I just find it odd that following the exact same procedure/keystrokes in IE creates local file with parentheses, while FF makes local files with substitution characters. I can go through the hassle of opening the file if it's a PDF, and doing a SaveAs. BUT, I don't have such an option when downloading/copying MP3 files (which also incur the substitute characters. SO - is this a natural byproduct of extracting the file name from the link script? (I inspected the file link and, in fact, the embedded file name IS modified.