Skip to content

Commit 8096306

Browse files
authored
Merge pull request #43 from CiscoM31/readme-fix
Change link to draft specification
2 parents d0b40a1 + fa90b4a commit 8096306

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
HTTP signatures provide a mechanism by which a shared secret key can be used to digitally "sign" a HTTP message to both verify the
55
identity of the sender and verify that the message has not been tampered with in-transit.
66

7-
This is done by contatinating the desired HTTP Headers together to form a string called a "Signing String". An encrypted
7+
This is done by concatenating the desired HTTP Headers together to form a string called a "Signing String". An encrypted
88
hash (digitial signature) is made of the Signing String using either an asymmetric algorithm (`rsa-sha256`) with a
99
public/private key pair or a symmetric algorithm (`hmac-sha256`) with a shared secret key.
1010

@@ -43,7 +43,7 @@ Add the following dependency to your Maven pom file.
4343
<dependency>
4444
<groupId>org.tomitribe</groupId>
4545
<artifactId>tomitribe-http-signatures</artifactId>
46-
<version>1.0</version>
46+
<version>1.5</version>
4747
</dependency>
4848
----
4949

@@ -169,7 +169,7 @@ return signer.sign(method, uri, headers);
169169

170170
== References
171171

172-
Signing HTTP Messages (Internet Draft 4) https://www.ietf.org/id/draft-cavage-http-signatures-04.txt
172+
Signing HTTP Messages (Internet Draft) https://tools.ietf.org/html/draft-ietf-httpbis-message-signatures-00
173173

174174
Instance Digests in HTTP http://tools.ietf.org/html/rfc3230
175175

0 commit comments

Comments
 (0)