httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Httpd Wiki] Update of "Compatibility" by wrowe
Date Wed, 28 Sep 2016 17:02:35 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.

The "Compatibility" page has been changed by wrowe:
https://wiki.apache.org/httpd/Compatibility

Comment:
Only the beginning of a long process, additional editors welcomed...

New page:
Apache HTTP Server implements a number of specifications, each of which poses interoperability
challenges for any implementor. Different implementations may;
 * Apply a different interpretation of the same reading when the specification is unclear
 * Choose to be permissive where multiple readings are possible, or to strictly conform when
the plain reading is clear
 * Deviate from the specification in error, for their own purpose, or to accommodate another
implementation

Apache HTTP Server since inception has erred on the side of being lenient in accepting questionable
input, and strict in emitting responses from the server, which helped to fuel the adoption
of the HTTP protocol. In response to a number of attack vectors which rely on the differences
in accepting and interpreting questionable input, the server is evolving to more strictly
require that input conform to the relevant specifications.

This wiki content attempts to catalog known compatibility questions between common HTTP servers,
browsers, other user-agents, and other proxy agents such as firewalls or load balancers. Note
that Apache HTTP Server acts as both a server, and as a proxy server, also as a user-agent
communicating with a back-end server. The implementation of the specs listed below may vary
between these two roles.

The current version of HTTP implements the following specifications (this list not exhaustive);
|| '''Spec''' || '''Title''' || '''Comments''' ||
|| [[https://tools.ietf.org/html/rfc7230|RFC 7230]] || Hypertext Transfer Protocol (HTTP/1.1):
Message Syntax and Routing ||  ||
|| [[https://tools.ietf.org/html/rfc7231|RFC 7231]] || Hypertext Transfer Protocol (HTTP/1.1):
Semantics and Content ||  ||
|| [[https://tools.ietf.org/html/rfc7232|RFC 7231]] || Hypertext Transfer Protocol (HTTP/1.1):
Conditional Requests ||  ||
|| [[https://tools.ietf.org/html/rfc7233|RFC 7231]] || Hypertext Transfer Protocol (HTTP/1.1):
Range Requests ||  ||
|| [[https://tools.ietf.org/html/rfc7234|RFC 7231]] || Hypertext Transfer Protocol (HTTP/1.1):
Caching ||  ||
|| [[https://tools.ietf.org/html/rfc7235|RFC 7231]] || Hypertext Transfer Protocol (HTTP/1.1):
Authentication ||  ||
|| [[https://tools.ietf.org/html/rfc3986|RFC 3986]] || URI Generic Syntax || By reference
of RFC 7230 ||

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Mime
View raw message