Commit f4b6e98f authored by David Golden's avatar David Golden

Reference RFC 7230-7235 instead of 2616

parent 878d4e6a
...@@ -7,6 +7,10 @@ Release notes for HTTP-Tiny ...@@ -7,6 +7,10 @@ Release notes for HTTP-Tiny
- Empty header fields are now allowed; headers with the 'undef' value - Empty header fields are now allowed; headers with the 'undef' value
will be rendered as an empty header. will be rendered as an empty header.
[DOCUMENTED]
- Updated HTTP/1.1 spec description from RFC 2616 to RFC 7230-7235
0.045 2014-07-19 23:17:28-04:00 America/New_York (TRIAL RELEASE) 0.045 2014-07-19 23:17:28-04:00 America/New_York (TRIAL RELEASE)
[FIXED] [FIXED]
......
...@@ -1573,9 +1573,20 @@ environment variables. ...@@ -1573,9 +1573,20 @@ environment variables.
=head1 LIMITATIONS =head1 LIMITATIONS
HTTP::Tiny is I<conditionally compliant> with the HTTP::Tiny is I<conditionally compliant> with the
L<HTTP/1.1 specification|http://www.w3.org/Protocols/rfc2616/rfc2616.html>. L<HTTP/1.1 specifications|http://www.w3.org/Protocols/>:
=for :list
* "Message Syntax and Routing" [RFC7230]
* "Semantics and Content" [RFC7231]
* "Conditional Requests" [RFC7232]
* "Range Requests" [RFC7233]
* "Caching" [RFC7234]
* "Authentication" [RFC7235]
It attempts to meet all "MUST" requirements of the specification, but does not It attempts to meet all "MUST" requirements of the specification, but does not
implement all "SHOULD" requirements. implement all "SHOULD" requirements. (Note: it was developed against the
earlier RFC 2616 specification and may not yet meet the revised RFC 7230-7235
spec.)
Some particular limitations of note include: Some particular limitations of note include:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment