You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The client would compose the signing string as:
(request-target): post /foo\n
(created): 1402170695
(expires): 1402170995
host: example.org\n
digest: SHA-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=\n
content-length: 18
It looks like "\n" is missing, or is this intentional?
(request-target): post /foo\n
(created): 1402170695\n
(expires): 1402170995\n
The text was updated successfully, but these errors were encountered:
sebastien-rosset
changed the title
Typo in section 4.1.1, RSA example
Typo in sections 4.1.1 and 4.1.2, RSA and HMAC examples
Jan 15, 2020
sebastien-rosset
changed the title
Typo in sections 4.1.1 and 4.1.2, RSA and HMAC examples
Typo in sections 3.1.2,, 3.1.3, 4.1.1 and 4.1.2, RSA and HMAC examples
Jan 15, 2020
sebastien-rosset
changed the title
Typo in sections 3.1.2,, 3.1.3, 4.1.1 and 4.1.2, RSA and HMAC examples
Typo in sections 3.1.2, 3.1.3, 4.1.1 and 4.1.2, RSA and HMAC examples
Jan 15, 2020
Section 4.1.1 has the following example:
It looks like "\n" is missing, or is this intentional?
The text was updated successfully, but these errors were encountered: