summaryrefslogtreecommitdiff
path: root/test/integration/test-bug-778375-server-has-no-reason-phrase
Commit message (Collapse)AuthorAgeFilesLines
* don't try to parse all fields starting with HTTP as status-lineDavid Kalnischkies2017-07-261-0/+2
| | | | | It is highly unlikely to encounter fields which start with HTTP in practice, but we should really be a bit more restrictive here.
* http(s): allow empty values for header fieldsDavid Kalnischkies2016-08-131-0/+1
| | | | | | | | | | | | 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
* tests: support spaces in path and TMPDIRDavid Kalnischkies2015-12-191-2/+2
| | | | | | | This doesn't allow all tests to run cleanly, but it at least allows to write tests which could run successfully in such environments. Git-Dch: Ignore
* tests: don't use hardcoded port for http and httpsDavid Kalnischkies2015-09-151-2/+2
| | | | | | This allows running tests in parallel. Git-Dch: Ignore
* derive more of https from http methodDavid Kalnischkies2015-03-161-0/+40
Bug #778375 uncovered that https wasn't properly integrated in the class family tree of http as it was supposed to be leading to a NULL pointer dereference. Fixing this 'properly' was deemed to much diff for practically no gain that late in the release, so commit 0c2dc43d4fe1d026650b5e2920a021557f9534a6 just fixed the synptom, while this commit here is fixing the cause plus adding a test.