summaryrefslogtreecommitdiff
path: root/spec/ruby/core/string/valid_encoding
diff options
context:
space:
mode:
authorPeteris Rudzusiks <rye@stripe.com>2025-06-12 15:59:12 +0200
committerHiroshi SHIBATA <hsbt@ruby-lang.org>2025-07-09 13:48:36 +0900
commit5d880b75efe75a2be7046e75ea62bd02e0cf94a5 (patch)
tree26a5601482de54705f62cc2d0673de7d78b177bc /spec/ruby/core/string/valid_encoding
parentaf6012b9427e182ac90de3591efa4ab9ac9e3fee (diff)
[rubygems/rubygems] Correctly sign S3 HEAD requests
We sometimes send HEAD requests. The s3_uri_signer.rb code allways assumed GETs. This lead to consistently getting 403 responses back from S3. Recently, S3 attempted to change the behaviour of how 403s are handled when TCP connections are reused, which escalated this bug from "just noise" to "breaks gem installs". They've reverted that behaviour, so the severity of this problem is back to "just noise". Either way, it's a bug in rubygems and warrants a fix it. https://github.com/rubygems/rubygems/commit/c38f502b73
Diffstat (limited to 'spec/ruby/core/string/valid_encoding')
0 files changed, 0 insertions, 0 deletions