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
Update example to be more HTTP-focused
#76
dret
closed
1 year ago
8
How should Accept header be used by the server?
#75
maricn
closed
1 year ago
4
"*" names for new members are not going to work in XML
#74
dret
closed
1 year ago
16
7807bis: outdent "}" in JSON content
#73
reschke
closed
1 year ago
0
Update JSON Schema refs to HTTP, etc.
#72
mnot
closed
1 year ago
0
replace mnot.com with example.com, etc
#71
richsalz
closed
1 year ago
0
murray's proposed change to "example.org"
#70
dret
opened
1 year ago
0
add missing curly brace
#69
reschke
closed
1 year ago
1
Switch the field to an Item
#68
mnot
closed
1 year ago
1
`Problem:` HTTP header field and localization
#67
benbucksch
closed
1 year ago
23
Translation
#66
benbucksch
closed
1 year ago
0
Avoid a default "type"
#65
benbucksch
closed
1 year ago
2
Uncertainty created by relative URIs used as IDs for problem "type" field
#64
benbucksch
closed
1 year ago
17
Resolveability text
#63
mnot
closed
1 year ago
2
Resolvability of IANA URIs
#62
mnot
closed
1 year ago
10
To do so
#61
mnot
closed
1 year ago
1
ARTART review
#60
mnot
closed
1 year ago
0
Add CDDL data definition for JSON form of problem object
#59
cabo
closed
1 year ago
3
Typos and other nits
#58
cabo
closed
1 year ago
1
Gen-ART editorial comment
#57
mnot
closed
1 year ago
2
Shouldn't parameters be semicolon-separated?
#56
awwright
closed
1 year ago
11
fix typo in abstract
#55
luchsamapparat
closed
2 years ago
1
Errata 5515: Clarification of meaning when type member is null
#54
darrelmiller
closed
2 years ago
1
nit: Summary of Changes section should provide greater detail on the motivation and changes
#53
darrelmiller
closed
2 years ago
0
nit: Introduction should briefly explain what has changed from 7807 and why
#52
darrelmiller
closed
2 years ago
0
nit: A later version of JSON Schema exists for the informative reference.
#51
darrelmiller
closed
2 years ago
1
nit: Abstract should mention that this document obsoletes RFC7807
#50
darrelmiller
closed
2 years ago
0
nit: Normative reference to HTTP spec needs to be updated to latest published document
#49
darrelmiller
closed
2 years ago
0
Add JSON-LD Context
#48
asbjornu
closed
1 year ago
9
Minor editorial change
#47
dret
closed
2 years ago
0
Last chance for comments
#46
richsalz
closed
2 years ago
12
Terminology review
#45
ioggstream
closed
2 years ago
0
Discuss usage of application/json
#44
dret
closed
2 years ago
3
Clarifying extension member scoping
#43
dret
closed
2 years ago
3
The validation-error example is wrong(!/?)
#42
olijaun
closed
2 years ago
0
Allow future standard extensions
#41
mnot
closed
2 years ago
0
Questions regarding extension
#40
olijaun
closed
2 years ago
5
Rough in a Problem HTTP field
#39
mnot
closed
2 years ago
2
Adjust registry policy
#38
mnot
closed
2 years ago
0
Multiple Problems adjustment
#37
mnot
closed
2 years ago
1
Forward compatibility
#36
awwright
closed
2 years ago
8
Mapping problem details into a header?
#35
mnot
closed
2 years ago
27
Requiring a specification document
#34
mnot
closed
2 years ago
2
Extension to show source of problem in request for 4xx class of errors
#32
sdatspun2
closed
2 years ago
15
Clarify `instance` dereferenceability
#31
asbjornu
closed
2 years ago
1
Multiple problems example
#30
sdatspun2
closed
2 years ago
8
Talk about non-resolveable type URIs
#29
mnot
closed
3 years ago
1
Explain how type errors for members are handled.
#28
mnot
closed
3 years ago
0
fix broken link into [SEMANTICS]
#27
reschke
closed
3 years ago
1
Recommendations about dereferenceability of type
#26
mnot
closed
3 years ago
1
Next