issues
search
ioggstream
/
draft-polli-resource-digests-http
THIS REPO WAS MOVED TO https://github.com/httpwg/http-extensions/
https://httpwg.org/http-extensions/draft-ietf-httpbis-digest-headers.html
Other
0
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add organization
#45
ioggstream
closed
5 years ago
0
Fix: #22. Use base64 to represent binary payloads
#44
ioggstream
closed
5 years ago
0
Fix: #36. Clarification on multiple digests values
#43
ioggstream
closed
5 years ago
0
Use ABNF.
#42
ioggstream
closed
5 years ago
1
Use ABNF for digest-header
#41
ioggstream
closed
5 years ago
0
Update author details
#40
LPardue
closed
5 years ago
0
Consider using multiformats (multihash) for future proofing
#39
dlongley
opened
5 years ago
6
Sign content-length to mitigate length-extension attacks
#38
ioggstream
closed
5 years ago
1
signing relevant representation metadata is mandatory
#37
ioggstream
opened
5 years ago
3
Managing multiple digest values
#36
ioggstream
closed
5 years ago
3
Digest of "empty" representation
#35
ioggstream
closed
5 years ago
3
Clarify digest-algorithm syntax
#34
ioggstream
closed
5 years ago
4
Define a different encoding for id-sha-*
#33
ioggstream
closed
5 years ago
1
Reformat algorithms
#32
ioggstream
closed
5 years ago
0
Fix typos
#31
ioggstream
closed
5 years ago
0
Threats brainstorming. #29
#30
ioggstream
opened
5 years ago
0
Create a threat model
#29
ioggstream
closed
5 years ago
2
wrap examples in block
#28
LPardue
closed
5 years ago
0
fix dangling reference
#27
LPardue
closed
5 years ago
0
uppercase an http
#26
LPardue
closed
5 years ago
0
typo in introduction
#25
LPardue
closed
5 years ago
0
Added IANA considerations for obsoleted algorithms. #16
#24
ioggstream
closed
5 years ago
0
Minor cleanups.
#23
ioggstream
closed
5 years ago
0
Define an encoding for binary payload data examples
#22
ioggstream
closed
5 years ago
1
Warnings in security considerations.
#21
ioggstream
closed
5 years ago
1
Using Digest in signatures
#20
ioggstream
closed
5 years ago
4
Deprecate broken-cryptographic algorithms.
#19
ioggstream
closed
5 years ago
1
Use http-core or 723x?
#18
ioggstream
closed
5 years ago
2
HTTP integrity is multi-layered.
#17
ioggstream
closed
5 years ago
1
Remove non-cryptographic algorithms
#16
ioggstream
closed
5 years ago
8
Elaborate on the use cases for a Digest
#15
jyasskin
opened
5 years ago
8
Introduction refers to TCP instead of TLS
#14
jyasskin
closed
5 years ago
7
"resource" wg doesn't exist
#13
jyasskin
closed
5 years ago
0
Carefully explained the checksum problem.
#12
ioggstream
closed
5 years ago
1
Formatting fixups
#11
LPardue
closed
5 years ago
0
Explicitly reference content-type and content-encoding in the proposal introduction.
#10
ioggstream
closed
5 years ago
2
Example for content-encoding importance
#9
ioggstream
closed
5 years ago
1
DISCOURAGES is not an RFC2119 keyword
#8
LPardue
closed
5 years ago
2
Refer to RFC8174
#7
LPardue
closed
5 years ago
0
Fix gh-pages
#6
LPardue
closed
5 years ago
0
"identity" is not a content coding
#5
ioggstream
closed
5 years ago
1
Investigate the usage of PATCH
#4
ioggstream
closed
5 years ago
2
GitHub pages is a little messed up
#3
LPardue
closed
5 years ago
4
Make this compliant with Markdown workflow
#2
LPardue
closed
5 years ago
1
Shorter abstract
#1
ioggstream
closed
5 years ago
0