Additional special characters in version_description causing 403 error
See original GitHub issueI’m getting a 403 error when deploying my application.
The problem seems to be my application version string 0.0.0-dev+440e3f0
which uses the +
character to add commit hash metadata to the version number (as permitted by the semver spec)
This looks to be the same issue as https://github.com/einaregilsson/beanstalk-deploy/issues/28 (and in particular @einaregilsson’s fix mentioned here addresses some special characters, but not +
).
Would it be possible to add +
to the list of allowed (and escaped) characters?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Special characters in URL leads to 403 - Stack Overflow
Try removing the query string 403 lines. It could work locally if you don't have mod alias enabled as those lines will be...
Read more >S3 Put fails with 403 if object's metadata has special character
Describe the bug Using Storage.put to upload objects with metadata that have special characters will fail with 403 Forbidden.
Read more >How to Fix a 403 Forbidden Error on Your WordPress Site
The 403 Forbidden error indicates that the server understood the request but refuses to authorize it. Find out more about the causes and...
Read more >What Is the 403 Forbidden Error and How to Fix It (8 Methods ...
2. Reset File and Directory Permissions. Another possible cause triggering HTTP 403 errors is incorrect permissions for files or folders. In general, when...
Read more >Searching for word with special characters results in 403 ...
On my WP-sites, when I search for words with special characters like “tëst” the result is a common white 403 server error page?!...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome! Thanks @einaregilsson!
Sorry, use v16 instead, that fixes some additional issues with * in version description and truncates commit messages that are too long to be used as a version description 🙂