Jeff King <peff@xxxxxxxx> writes: >> I suspect this could all be done as a CGI wrapping git-http-backend. You >> can influence the HTTP response code by sending: > ... > And here's a minimally worked-out example of that approach. It's on top > of your patches so I could use your credential-helper infrastructure in > the test, but the intent is that it would replace all of the test-tool > server patches and be rolled into t5556 as appropriate. Thanks for helping Matthew's topic move forward. I very much like seeing apache used for tests in this sample approach, like all the other http tests we do with apache, instead of a custom server that we need to ensure that it mimics the real-world use cases and we have to maintain.
