| commit | e31165ce69ef3986e8b5477d52cc7d4e19b4212d | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Mon, 9 May 2016 06:19:00 +0000 (9 08:19 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 10 May 2016 17:28:01 +0000 (10 10:28 -0700) | ||
| tree | b433d37f2e6dd4fd39f5f48d3fcb7256fec5510b | treesnapshot (tar.gz zip) |
| parent | f1f2b45be0a2b205fc07758e0f4e9c13e90d34d9 | commitdiff |
t5551: make the test for extra HTTP headers more robust
To test that extra HTTP headers are passed correctly, t5551 verifies that
a fetch succeeds when two required headers are passed, and that the fetch
does not succeed when those headers are not passed.
However, this test would also succeed if the configuration required only
one header. As Apache's configuration is notoriously tricky (this
developer frequently requires StackOverflow's help to understand Apache's
documentation), especially when still supporting the 2.2 line, let's just
really make sure that the test verifies what we want it to verify.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Reviewed-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
To test that extra HTTP headers are passed correctly, t5551 verifies that
a fetch succeeds when two required headers are passed, and that the fetch
does not succeed when those headers are not passed.
However, this test would also succeed if the configuration required only
one header. As Apache's configuration is notoriously tricky (this
developer frequently requires StackOverflow's help to understand Apache's
documentation), especially when still supporting the 2.2 line, let's just
really make sure that the test verifies what we want it to verify.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Reviewed-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t5551-http-fetch-smart.sh | diffblobblamehistory |