This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 30
Validate crypto headers #456
Comments
+1000 |
Depends on #379. |
jrconlin
added a commit
that referenced
this issue
May 10, 2016
Add primative header checking, and normalize tests to only send proper header values (unless explicity checking for that). Closes #456
jrconlin
added a commit
that referenced
this issue
May 10, 2016
Add primative header checking, and normalize tests to only send proper header values (unless explicity checking for that). Closes #456
jrconlin
added a commit
that referenced
this issue
Aug 12, 2016
Check the encryption headers to make sure they're roughly valid before passing them on to the client. Closes #456
jrconlin
added a commit
that referenced
this issue
Aug 12, 2016
Check the encryption headers to make sure they're roughly valid before passing them on to the client. Closes #456
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@jrconlin brings up a great point in #452 (comment):
We can also help developers by rejecting invalid or incomplete
Encryption
(andContent-Encoding
) headers, like we already do forCrypto-Key
. May as well reject early with an informative error instead of storing and delivering a message that the client will drop immediately.The text was updated successfully, but these errors were encountered: