diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2016-08-12 22:13:09 +0200 |
|---|---|---|
| committer | Julian Andres Klode <jak@debian.org> | 2016-10-05 21:53:38 +0200 |
| commit | c0475a2283d662a375295c1477d7193cef823832 (patch) | |
| tree | dbc40bc1b5a65062b25a5de6a860cbfc3a8d2143 /test/integration/test-bug-747261-arch-specific-conflicts | |
| parent | bc8c6ca0c1815b1c3141c177939e1efbdc9862e9 (diff) | |
http(s): allow empty values for header fields
It seems completely pointless from a server-POV to sent empty header
fields, so most of them don't do it (simply proven by this limitation
existing since day one) – but it is technically allowed by the RFC as
the surounding whitespaces are optional and Github seems to like sending
"X-Geo-Block-List:\r\n" since recently (bug reports in other http
clients indicate July) at least sometimes as the reporter claims to have
seen it on https only even through it can happen with both.
Closes: 834048
(cherry picked from commit 148c049150cc39f2e40894c1684dc2aefea1117e)
Diffstat (limited to 'test/integration/test-bug-747261-arch-specific-conflicts')
0 files changed, 0 insertions, 0 deletions