| 1 |
-*- text -*- |
| 2 |
|
| 3 |
This document attempts to list RFC requirements and determine whether |
| 4 |
neon meets them, or where they do not apply, etc. |
| 5 |
|
| 6 |
Yes: test written, succeeds |
| 7 |
No: test written, but currently fails |
| 8 |
???: no test written |
| 9 |
---: feature not supported |
| 10 |
App: this is an application issue not a neon issue |
| 11 |
|
| 12 |
RFC2616 |
| 13 |
======= |
| 14 |
|
| 15 |
3.1: MUST treat major/minor as separate digits Yes |
| 16 |
3.1: MUST ignore leading zeros Yes |
| 17 |
3.1: MUST only send HTTP/1.1 when appropriate ??? |
| 18 |
|
| 19 |
3.2.2: MUST use abs_path of "/" in Request-URI App |
| 20 |
3.2.3: comparisons of host names MUST be case-insensitive Yes |
| 21 |
comparisons of scheme names MUST be ... Yes |
| 22 |
comparison of empty abs_path equivalent to "/" No/--- |
| 23 |
|
| 24 |
3.3.1: MUST accept three date formats App/Yes [2] |
| 25 |
MUST only generate RFC1123-style dates App |
| 26 |
|
| 27 |
3.3.1: MUST use GMT for http-dates ??? |
| 28 |
MUST assume GMT when parsing asctime dates ??? |
| 29 |
|
| 30 |
3.4.1: MUST respect charset label provided Yes/App |
| 31 |
|
| 32 |
3.5*: content codings App |
| 33 |
|
| 34 |
3.6: MUST requirements for multiple transfer-codings --- [4] |
| 35 |
|
| 36 |
3.6.1: parsing of chunked transfer coding Yes |
| 37 |
MUST be able to handle "chunked" transfer-coding Yes |
| 38 |
MUST ignore unknown chunk-extension extensions Yes |
| 39 |
|
| 40 |
3.7: parsing of Content-Type headers Yes |
| 41 |
|
| 42 |
3.7: MUST NOT have LWS between type/subtype in C-T hdr App |
| 43 |
SHOULD only send parameters to "new HTTP apps" (>1.0?) App |
| 44 |
|
| 45 |
3.7.1: MUST represent HTTP message in canonical form App |
| 46 |
MUST accept CRLF/CR/LF as line-breaks in text/* media App |
| 47 |
MUST NOT use only CR or LF in HTTP control structures ??? |
| 48 |
MUST specify charset if not ISO-8859-1 App |
| 49 |
|
| 50 |
3.7.2: multipart types --- |
| 51 |
|
| 52 |
3.8: SHOULD have short product token Yes/App [5] |
| 53 |
SHOULD use product-version for version identifier Yes/App |
| 54 |
only product-version differs between versions Yes/App |
| 55 |
|
| 56 |
3.9: Content Negotiation ---/App |
| 57 |
|
| 58 |
3.10: Language Tags ---/App |
| 59 |
|
| 60 |
3.11: Entity Tags ---/App |
| 61 |
|
| 62 |
|
| 63 |
|
| 64 |
|
| 65 |
|
| 66 |
[2]: date parser is provided which handles all three formats, but no |
| 67 |
handling of the Date header is present within neon. |
| 68 |
|
| 69 |
[3]: not sure if neon should be handling of this internally. |
| 70 |
|
| 71 |
[4]: neon only supports using just chunked Transfer-Coding or none. |
| 72 |
|
| 73 |
[5]: these reflect that applications may add their own product tokens |
| 74 |
alongside neon's. |