On Tue, Mar 9, 2010 at 1:27 PM, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote: > Ryan Phillips <ryan@xxxxxxxxxxxxx> wrote: >> I'm trying to follow the git-http-backend man page on setting up >> authenticated pushes to my apache server. Pulls work fine, and fully >> authenticated pushes work fine. However, when I try and setup >> anonymous pulls and authenticated pushes the push fails. >> >> I believe the culprit is this 403 error: >> >> 192.168.1.1 - - [09/Mar/2010:09:01:43 -0800] "GET >> /git/test.git/info/refs?service=git-receive-pack HTTP/1.1" 403 - "-" >> "git/1.7.0.2.dirty" > > Ugh. Looks like I didn't design this thing right. > > The backend wants you to be authenticated before it will service > the git-receive-pack advertisement. Even though its the same > data as the git-upload-pack advertisement (but slightly different > capability strings). > > Maybe we should consider doing something like this patch so that > the advertisement under info/refs?service=git-receive-pack can be > sent without needing authentication. My only hesitation is this > makes it harder for the client to setup the authentication before > it needs to transmit the pack file, which may mean it needs to send > the pack twice. > Thank you everyone for your response. Shawn: That patch does fix the issue for now. Regards, Ryan -- 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