From 1646352f3c539d0592d4930748d8fb77c0af4ef4 Mon Sep 17 00:00:00 2001 From: Tatsuhiro Tsujikawa Date: Tue, 24 Feb 2015 14:48:58 +0900 Subject: [PATCH] Update doc --- doc/apiref-header.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/apiref-header.rst b/doc/apiref-header.rst index 79542028..754f726b 100644 --- a/doc/apiref-header.rst +++ b/doc/apiref-header.rst @@ -71,7 +71,13 @@ request headers must not include more than one "Host" header field. Each header field name and value must obey the field-name and field-value production rules described in `RFC 7230, section 3.2. `_. -Additionally, all field name must be lower cased. +Additionally, all field name must be lower cased. While the pseudo +header fields must satisfy these rules, we just ignore illegal regular +headers (this means that these header fields are not passed to +application callback). This is because these illegal header fields +are floating around in existing internet and resetting stream just +because of this may break many web sites. This is especially true if +we forward to or translate from HTTP/1 traffic. With the above validations, nghttp2 library guarantees that header field name passed to `nghttp2_on_header_callback()` is not empty.