-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forms with unicode file names fail upload #196
Comments
When I look at the browser console, I see the error message
Reading about it, I think the issue has to do with the Is a form ID allowed to contain a non-ASCII character? If so, then I think we should encode the filename before specifying it in the header. Probably percent-encoding would be easiest? Frontend would need to encode the header, and pyxform-http would need to decode it, but I'm not sure that Backend would need to change. We generally encode form IDs throughout Central, and Enketo links in Central use tokens separate from the form ID, so hopefully this would be a one-off change. |
Yes, it is. Your analysis seems right to me and percent-encoding between frontend and |
Sounds good! @yanokwa, are you able to add percent-decoding to |
As an update, as part of v1.2, we will have a new header, |
Related: getodk/collect#4554 |
Test file: tést.xlsx.zip
Central reports
Something went wrong: there was no request.
Here's what I know so far...
curl --request POST --data-binary @/path/to/tést.xlsx http://127.0.0.1:5000/api/v1/convert
My gut says this is some interaction with Central and pyxform-http.
The text was updated successfully, but these errors were encountered: