Releases: Visma-AutoPay/http-signatures
Releases · Visma-AutoPay/http-signatures
1.3.1
Implemented specifications
Changes
- Links in README and Javadoc updated to point to RFC documents instead of the drafts
1.3.0
Implemented specifications
Changes
- Added support for
HttpServletRequest
andHttpServletResponse
when creating Signature context:- targetUri(servletRequest.getRequestURL(), servletRequest.getQueryString())
- headers(servletRequest.getHeaderNames(), servletRequest::getHeaders)
- headers(servletResponse.getHeaderNames(), servletResponse::getHeaders)
1.2.0
Implemented specifications
Changes
- Implemented support for trailer fields and related
tr
signature parameter. See Trailer Fields. - Changed encoding of path and query
- Percent-encoded octets are not decoded for
@target-uri
,@path
,@request-target
and@query
components. See Path and Query. - Percent-encoded octets in
@query-param
are re-encoded. See Query Parameters.
- Percent-encoded octets are not decoded for
- Exception is thrown for unknown or "illegal" component parameters when verifying signature. For example,
foo
parameter for any component orkey
for@query
will trigger an exception. - "Canonicalized Structured HTTP Fields" term changed to "Strict Serialization of HTTP Structured Fields"
SignatureComponents.Builder.structuredHeader()
method renamed tostructuredHeader()
SignatureComponents.Builder.relatedRequestCanonicalizedHeader()
method renamed torelatedRequestStructuredHeader()
1.1.0
Implemented specifications
Changes
- Implemented
tag
signature parameter. See Signature Parameters. - Implemented
ecdsa-p384-sha384
signature algorithm. See ECDSA using curve P-384 DSS and SHA-384.