On Mon, Oct 3, 2011 at 8:47 PM, Jeff King <peff@xxxxxxxx> wrote: >> To me, just "<service>: access denied" is enough. Not particularly >> friendly but should be a good enough clue. > > Yeah, maybe. Certainly it's better than "the remote end hung up > unexpectedly". > > However, the leakage is still there. You would get "the remote hung up" > for no-such-repo, and "access denied" for this. Or were you just > proposing that _all_ errors give "access denied". Certainly it's better > than just hanging up, too, and there is no leakage there. All of them. At least it's good to know my request has reached (and rejected by) the server, not dropped on the floor by some random firewall along the line. > It might be nice to default to that, and let sites easily enable > friendlier messages, though. I'm thinking of passing "verbose" option back to server to get more helpful messages, the option would be turned off by default. It's up to admin to decide (would be actually helpful during deployment test, for example). Or is it possible already? -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html