aws-sign4 icon indicating copy to clipboard operation
aws-sign4 copied to clipboard

Common Lisp library for Amazon Web Services signing version 4

Results 5 aws-sign4 issues
Sort by recently updated
recently updated
newest added

In GET requests one must provide :payload "" in order to generate valid signatures. This is confusing and unnecessary. This creates an invalid signature: (aws-sign4:aws-sign4 :region :us-east-1 :service "route53" :method...

AWS requests were failing in certain cases, the spec for canonicalizing the query string says: > Sort the parameter _names_ by character code point in ascending order This PR sorts...

Flexi-streams on windows by default encodes a newline character as two bytes (CRLF), when AWS expects just LF. This changes the hash of the canonical request, so invalidates the signature.

Payloads are often large in size, and streaming would be better in those cases. However, since aws-sign4 currently only accepts octets in the payload, the entire file needs to be...

ASDF3 recommends a single primary system per `.asd` file (e.g., `FOO`), with other, optional subsystems being named with a slash (e.g., `FOO/BAR`). This ensures that `FOO/BAR` can be loaded without...