On Aug 27, 2012, at 04:28 , Iain Paton wrote:
> On 26/08/12 10:57, Iain Paton wrote:
>
>>
>
> I've just discovered that the directive only appears in apache 2.4
> so something more generic will probably be a better idea. Not everyone will
> be running 2.4.x for a while yet.
You coul
On 26/08/12 10:57, Iain Paton wrote:
>
I've just discovered that the directive only appears in apache 2.4
so something more generic will probably be a better idea. Not everyone will
be running 2.4.x for a while yet.
Iain
--
To unsubscribe from this list: send the line "unsubscribe gi
On 26/08/12 11:13, Jeff King wrote:
> Yeah, I'm surprised it took this long to come up, too. Perhaps most
> people just do anonymous http, and then rely on ssh for pushing to
> achieve the same effect. Or maybe my analysis of the problem is wrong.
> :)
I'd be using ssh to push too, but the simple
On Sun, Aug 26, 2012 at 10:57:59AM +0100, Iain Paton wrote:
> > The odd URL is because we are probing to see if the server even supports
> > smart-http. But note that it does not match your regex above, which
> > requires "/git-receive-pack". It looks like that is pulled straight from
> > the git-
On 25/08/12 21:39, Jeff King wrote:
> I think your regex is the culprit. The first request comes in with:
>
>>> GET /git/test.git/info/refs?service=git-receive-pack HTTP/1.1
>
> The odd URL is because we are probing to see if the server even supports
> smart-http. But note that it does not match
On Sat, Aug 25, 2012 at 03:56:01PM +0100, Iain Paton wrote:
> > It's like the initial http requests do not get a 401, and the push
> > proceeds, and then some later request causes a 401 when we do not expect
> > it. Which is doubly odd, since we should also be able to handle that
> > case (the fir
On Fri, Aug 24, 2012 at 09:19:28PM +0100, Iain Paton wrote:
> A recent update to git 1.7.12 from 1.7.3.5 seems to have changed
> something - trying to push to a smart http backend no longer prompts
> for a password and hence fails the server auth.
> [...]
> Backtracking through the versions I've s
Hi List,
A recent update to git 1.7.12 from 1.7.3.5 seems to have changed something -
trying to push to a smart http backend no longer prompts for a password and
hence fails the server auth.
The server is currently running git 1.7.9 behind apache 2.4.3 with an almost
verbatim copy of the apach
8 matches
Mail list logo