All Versions
Latest Version
Avg Release Cycle
21 days
Latest Release
2413 days ago

Changelog History

  • v0.7.2 Changes

    November 07, 2017
    • Formatting changes
  • v0.7.1 Changes

    November 07, 2017
    • โœ… Skipping tests related to duplicate query parameters. The AWS Signature V4 specs don't have any information on how to deal with them. (issue #10)
  • v0.7.0 Changes

    August 07, 2017

    ๐Ÿ›  Fixes:

    • โœ‚ Removed Mix.env reference that caused problems with distillery based releases. PR from zeroasterisk (issue #8)
  • v0.6.0 Changes

    ๐Ÿ›  Fixes:

    • โœ… Enabled AWS Secure Token tests (post-sts-token). Use the AWS STS service to obtain temporary credentials and the corresponding session token. Use the temporary credentials to sign. The session token must be included as a request header or query string parameter X-Amz-Secure-Token.

    All AWS Signature V4 tests in the testsuite pass. (Exceptions: post-vanilla-query-nonunreserved and post-vanilla-query-space. These tests seem to be wrong.)

    AWS STS are supported only in request signing. They are not supported in the verifier (plug_sigaws).

    (AWS STS Ref)

  • v0.5.0 Changes

    June 05, 2017

    ๐Ÿ›  Fixes:

    • ๐Ÿ– Handle normalization of path segments during signature computation (issue #6)

    The normalize-path tests in the AWS Signature V4 testsuite pass with with fix.

  • v0.4.0 Changes

    June 05, 2017

    ๐Ÿ›  Fixes:

    • 0๏ธโƒฃ Default to "/" when path component not present in URL
  • v0.3.1

    May 28, 2017
  • v0.3.0 Changes

    May 28, 2017

    ๐Ÿ›  Fixes:

    • โœ… aws-sig-v4-testsuite/get-header-value-multiline test fails (issue #3)

    Canonical value computation for request headers with multiline values was not correct. Becuase of that the corresponding AWS Signature V4 testsuite was failing. Fixed this issue.

    • โšก๏ธ AWS testsuite URL changed - Update (issue #4)
  • v0.2.0 Changes

    April 09, 2017

    โœจ Enhancements:

    • ๐Ÿ‘Œ Support precomputed content hash (issue #2)

    ๐Ÿ›  Fixes:

    • Correct "cryto" to "crypto" (issue #1)
  • v0.1.0

    April 09, 2017