issues
search
ietf-wg-httpapi
/
rfc7807bis
Revision of RFC7807: HTTP Problem Details
Other
20
stars
8
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Cardinality of problem details object members
#25
tdonker
closed
3 years ago
5
Propose IANA registry
#24
mnot
closed
3 years ago
1
adding processing model (closing #19)
#23
dret
closed
3 years ago
3
all predefined members are optional
#22
dret
closed
2 years ago
1
provide guidance for intentionally non-dereferencable URIs
#21
dret
closed
3 years ago
3
Warn about relative URIs in "type" and "instance"
#20
mnot
closed
3 years ago
0
Handling invalid problem objects
#19
mnot
closed
3 years ago
3
Added JSON schema
#18
sdatspun2
closed
3 years ago
1
fix metadata
#17
reschke
closed
3 years ago
1
Deprecating media type?
#16
sdatspun2
closed
3 years ago
5
Provide an indication of whether a type URL is designed to be dereferenced for documentation
#15
pimterry
closed
3 years ago
14
Consider discouraging relative path URLs in the 'type' field
#14
pimterry
closed
3 years ago
4
Make a clear recommendation for the 'type' to use when not linking to a documentation URL
#13
pimterry
closed
3 years ago
8
Problem Details Object for Warning
#12
sdatspun2
closed
2 years ago
22
Should 'type' definitely be required to be a URI?
#11
pimterry
closed
3 years ago
33
JSON-LD Context
#10
asbjornu
closed
2 years ago
43
Should `instance` be deprecated?
#9
sdatspun2
closed
3 years ago
3
Should JSON schema be used to describe Problem Details Object?
#8
sdatspun2
closed
3 years ago
11
Repository of common Problem types
#7
sazzer
closed
3 years ago
17
Multiple problems
#6
mnot
closed
2 years ago
27
Incorporate errata
#5
mnot
closed
3 years ago
1
Deprecate XML?
#4
mnot
closed
3 years ago
2
Validate HTTP message examples
#3
mnot
closed
3 years ago
0
IANA considerations
#2
mnot
closed
3 years ago
0
Update references
#1
mnot
closed
3 years ago
1
Previous