Some characters are not encoded in the response #331

Closed
opened 2026-01-19 18:29:55 +00:00 by michael · 1 comment
Owner

Originally created by @vitorgalvao on GitHub.

$ curl --silent --upload-file 'file with spaces?.txt' https://transfer.sh/
https://transfer.sh/RYw9k/file%20with%20spaces?.txt

Notice how the spaces were correctly encoded (%20), but the question mark was not (should have been %3F). This then causes problems when trying to access the given URL, as it shows as not existing.

The upload did work, and the file does exist at the correct location (https://transfer.sh/RYw9k/file%20with%20spaces%3F.txt), it’s just the returned response that shows incorrect information.

Characters confirmed to not get encoded:

  • ? (%20)
  • # (%23)
Originally created by @vitorgalvao on GitHub. ``` $ curl --silent --upload-file 'file with spaces?.txt' https://transfer.sh/ https://transfer.sh/RYw9k/file%20with%20spaces?.txt ``` Notice how the spaces were correctly encoded (`%20`), but the question mark was not (should have been `%3F`). This then causes problems when trying to access the given URL, as it shows as not existing. The upload did work, and the file does exist at the correct location (`https://transfer.sh/RYw9k/file%20with%20spaces%3F.txt`), it’s just the returned response that shows incorrect information. Characters confirmed to not get encoded: * `?` (`%20`) * `#` (`%23`)
Author
Owner

@paolafrancesca commented on GitHub:

@vitorgalvao addressed in #125

@paolafrancesca commented on GitHub: @vitorgalvao addressed in #125
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#331