Twenty-eight questions, and no twenty-ninth
This service answers a fixed set over six IETF RFCs. There is no free-text input: the questions below are the whole surface, which is what lets every answer replay a committed draft and rerun the grounding check with no model on the request path.
Each answer is a list of claims, and each claim names the passage that is supposed to support it. A check decides, per claim, whether that passage actually does — and the claims that fail are shown to you with the rule that dropped them rather than quietly deleted.
In the corpus — annotated with the sections that should support the answer
- q01 Which characters make up the unreserved set in a URI? expects rfc3986#2.3
- q02 How is a percent-encoded octet written in a URI? expects rfc3986#2.1
- q03 What does a URI fragment identifier identify? expects rfc3986#3.5
- q04 Which HTTP request methods are defined as safe? expects rfc9110#9.2.1
- q05 Which status code means the server knows the request method but the target resource does not support it, and what must that response include? expects rfc9110#15.5.6
- q06 What distinguishes a strong validator from a weak validator? expects rfc9110#8.8.1
- q07 What does a Vary header field on a response tell a cache? expects rfc9110#12.5.5
- q08 How is a quality value in a content negotiation header field interpreted? expects rfc9110#12.4.2
- q09 How does a server indicate that it supports range requests for a resource? expects rfc9110#14.3
- q10 How does a cache calculate the freshness lifetime of a stored response? expects rfc9111#4.2.1
- q11 When may a cache use heuristic freshness? expects rfc9111#4.2.2
- q12 What does the s-maxage response directive do, and which caches does it apply to? expects rfc9111#5.2.2.10
- q13 When may a shared cache store a response to a request that carried an Authorization header field? expects rfc9111#3.5
- q14 How does a recipient determine the length of a message body in an HTTP/1.1 message? expects rfc9112#6.3
- q15 How is the end of a chunked message body signalled? expects rfc9112#7.1
- q16 Which request-target form is used for a CONNECT request? expects rfc9112#3.2.3
- q17 What effect does the HttpOnly attribute have on a cookie? expects rfc6265#5.2.6
- q18 How is domain matching defined for cookies? expects rfc6265#5.1.3
- q19 What minimum size per cookie should a user agent support? expects rfc6265#6.1
- q20 What are the six structural characters in JSON? expects rfc8259#2
Not in the corpus — annotated with the failure state each should land in
- u01 How does HTTP/2 multiplex multiple requests over a single TCP connection? expects partial
- u02 What fields does an HTTP/2 HEADERS frame contain? expects unsupported
- u03 How does the SameSite cookie attribute restrict cross-site requests? expects unsupported
- u04 What grant types does OAuth 2.0 define? expects unsupported
- u05 How is the signature of a JSON Web Token computed? expects unsupported
- u06 What resource records does a DNS server return for an A-record query? expects unsupported
- u07 What is the message sequence of the TLS 1.3 handshake? expects unsupported
- u08 How does a browser decide whether to send a CORS preflight request? expects unsupported