• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

aws / aws-sdk-core-ruby / 248 / 8
100%
master: 100%

Build:
DEFAULT BRANCH: master
Ran 13 Aug 2014 08:17PM UTC
Files 107
Run time 49s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

13 Aug 2014 07:54PM UTC coverage: 92.089% (+0.4%) from 91.662%
2.1.2, NOKOGIRI=1, Gemfile

push

travis-ci

trevorrowe
Now requesting S3 url-encode all keys by default.

Amazon S3 supports uploading objects with keys that can not
be safely returned in XML responses, such as ascii 0-10.
These keys cause the SDK to fail when attempting to parse
XML if one such key is present.

To support these keys, S3 accepts a Encoding-Type header. When set,
S3 will url encode all keys in the response XML.

This commit adds a plugin, that sets this request parameter by
default. It then also url-decodes keys automatically before
returning the response data. This makes it so the key handling
is hands-off.

If the user specifies the `:encoding_type` request parameter,
then the plugin is disabled, and the decoding of the keys is
left as an exercise for the user. This is required to be
backwards compatible. This also ensures that if S3 specifies
new encoding types in the future, this will not break.

Fixes #95

3143 of 3413 relevant lines covered (92.09%)

87.19 hits per line

Source Files on job 248.8 (2.1.2, NOKOGIRI=1, Gemfile)
  • Tree
  • List 0
  • Changed 58
  • Source Changed 6
  • Coverage Changed 57
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 248
  • Travis Job 248.8
  • a632f575 on github
  • Prev Job for 2.1.2, NOKOGIRI=1, Gemfile on master (#246.8)
  • Next Job for 2.1.2, NOKOGIRI=1, Gemfile on master (#249.8)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc