-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JWS url calculation can't handle absoluteURI form Request-URIs #341
Comments
Huh, that's really interesting! I was not aware of the absoluteURI form, let alone the RFC requirement to implement it. |
I ran into this bug as well, just now; the ACME client I was testing sent a full URL rather than a path. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://tools.ietf.org/html/rfc2616#section-5.1.2
Curiously, this seems to have come up twice in recent times on the forums.
(Excuse the scheme mismatch, I hacked Pebble a little to make packet captures easier, I promise the same thing happens on
master
).I checked and Let's Encrypt is unaffected, probably because the nginx frontend or whatever is dealing with it. Bare Boulder might have the same behavior as Pebble, but I didn't check.
The text was updated successfully, but these errors were encountered: