Hi!
While testing the export config file feature, I noticed a typo in the file created.
The . between filename and its extension is replaced by %2E
Installed package: duplicati-2.1.0.105_canary_2025-01-07-osx-arm64-cli.pkg
Hi!
While testing the export config file feature, I noticed a typo in the file created.
The . between filename and its extension is replaced by %2E
Installed package: duplicati-2.1.0.105_canary_2025-01-07-osx-arm64-cli.pkg
Welcome to the forum @macSOSfr
Not reproducible on Windows 10 with Edge browser. File automatically downloads like:
What browser are you using, and is GUI a localhost connection or possibly via a proxy?
If test
backup is pretty small, you can also try Create bug report
to see if it fails too.
Does your browser have any developer tools to watch the network traffic? Is this Safari?
You may want to avoid percent escape sequences in
filename
, because they are handled inconsistently across browsers. (Firefox and Chrome decode them, while Safari does not.)
2.0.8.1 sends:
attachment; filename=test-duplicati-config.json
2.1.0.105 sends:
attachment; filename=test-duplicati-config%2Ejson
I donât think itâs a typo. Itâs probably Percent-encoding. ASCII codepoint for period is 2E.
Thank you. I knew it was OK on Windows.
Browser is Safari on a freshly installed VM with macOS Sonoma 14.7.2
Bug report as you suggested is just fine.
Just installed Brave and Firefox, and the name of the file is rightly formated with the Export config feature.
That one has Duplicati saying this to Edge:
Content-Disposition: attachment; filename=bugreport.zip
so whatever is seemingly percent-encoding period didnât in this case.
Regardless, a developer will need to look, but I might reclassify this topic to Support anyway.
On the same thread, the âRight-click and choose Save AsâŚâ with Safari offers a filename set to âexportâ without the .json extension. The extension must added in the popup or manually by renaming in Finder
With Firefox, it saves as export.json
Narrowed issue down to seeming introduction in 2.0.9.102 which changed a lot in this area.
Most notably, I think itâs when the web server changed to Kestrel. Thatâs all the clues I have.
I have tracked it down and created an issue for it.
Thanks for reporting, I have created an issue and this will be fixed.
Youâre welcome. Thank you.