A user, Benjamin_D, is experiencing a “broken pipe” error when uploading a PDF file with a name containing special characters (e.g., é, ï) to a S3 clone. The error only occurs with PDF files, as a JPEG file with the same name works fine. Benjamin_D suspects the issue is related to the content_disposition formatting in the s3_store.rb file and suggests a fix.
Martin agrees with the diagnosis and promises to submit a PR to fix the issue. Later, Martin confirms that a fix is being implemented and provides a link to the PR: https://github.com/discourse/discourse/pull/10108. The fix has been tested and is working fine with the problematic PDF file name.
latest app, I rebuilt an hour ago, I can’t repro on meta, I assume it has to do with French localization.
I have a broken pipe error when I try to upload a pdf name laïcité.pdf but the same one renamed laicite.pdf works fine.
laïcité.jpg works also fine.
something named décroissance.pdf gives a different error “we encountered an internal error. please try again.”
ps. Not sure if it’s pertinent, I also use an S3 clone (scaleway) which also gave me a broken pipe error when I tried rake uploads.migrate_to_s3, but feels unrelated.
pps. yep.. it might be related to the S3 clone upload, I checked I have a 3 weeks old upload with an accent, just prior of the enabling of the S3 upload option
I think you are right, these kind of issues with filenames always slip my mind. I should be able to get a PR up to fix this tomorrow. Thanks for the report!
. The fix will land soon!