Johannes Schindelin <johannes.schinde...@gmx.de> writes: > Testing the headers? I dunno, do we have tests for that already? I thought > we did not: it requires an HTTP server (so that the headers are actually > sent) that we can force to check the header... > > So I see we have some tests that use Apache, and one that uses our own > http-backend. But is there already anything that logs HTTP requests? I did > not think so, please correct me if I am wrong.
I suspect that no codepath in the current system has cared about what http headers are sent; auth stuff might have but even then I would imagine that a test for auth would observe the end result (i.e. it would ask "did the server accept or reject us?") not the mechanism (i.e. it would not ask "did we correctly send an Authorization header?"). So I wouldn't be surprised if this topic is the first one that cares exactly what headers are sent out (eh, rather, "we told Git to send this and that header, do they appear at the server end?"), in which case it is very likely that we do not have any existing test that can be imitated for that purpose X-<. In other words, the answer to "Do we already have a test so that I can mimick it instead of thinking of a way to test this?" would probably be "No". Do we care about this feature deeply enough to devise a mechanism to prevent it from getting broken by careless others in the future? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
