404 when key contains slash
See original GitHub issueI think this has the same root cause as #43, except I am using my own custom string with slash (tmp release/benchmark
) and receives 404 when trying to save the cache.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Trailing slash causes 404, can I fix using htaccess?
The first line says: "if it's not a directory" (because then a trailing slash would have meaning). The second line says: redirect everything...
Read more >CloudFront / S3 returning 404 when no trailing slash : r/aws
It appears if I don't add a trailing slash, cloudfront or s3 just assuming I'm looking for testblog.html, which is a file that...
Read more >S3 client doesn't handle object keys with leading or ...
Given object keys like //foo , or foo//bar , the S3 client reports a 404 not found error even when the key exists....
Read more >Commit list returns 404 on branches whose names contain ...
Merge requests whose source branch name contains a forward slash suggested that the source branch did not exist ("source branch does not ...
Read more >How can I troubleshoot the 404 "NoSuchKey" error ... - YouTube
How can I troubleshoot the 404 "NoSuchKey" error from Amazon S3? · Key moments. View all · Key moments · Description · Key...
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
The fix for the
/
issue has been deployed:The fix for other special characters such as
+
and%
is still in progress.@alexlamsl @fsimonis while it’s true that there isn’t a replace expression function that would help here, you should be able to use
::set-output
withsed
or similar to do string replacement as a workaround. e.g.Not the most ideal workaround, but unless I’m misunderstanding hopefully that’ll work for you in the meantime!
Just an update, we’re rolling out a fix on the server-side for this sometime today or early next week.