can pull - cannot push - with or without hgrc(?) auth issues

[Paul Boddie]

John Stean wrote:
> Hello, thanks for the help so far on this. I am so close to having 
> this set up, but having one last issue.
>
> I can pull from my new repository over https, and form this I have to 
> provide uname and password that I set up using htpasswd.

This would suggest that the Apache mechanisms are working.

[...]

> WITH hgrc the only difference is the final auth returns:
> abort: HTTP Error 500: Internal error
>
> I have tried no hgrc file
> an hgrc file with and without [path] (I only need [path] section for a 
> pull dont i?)
> I have tried adding the https uname password in an [auth] section, no 
> change

The username and password should only be of concern to Apache, since it 
is the Web server which controls the authentication.

> Whenever I have the hgrc file, it throws a 500 response for the last 
> auth, and without the hgrc file it just returns authorization failed.
>
> Can you offer any help here please? I am wondering if this is an 
> apache setup issue rather than mercurial?

With 500 errors, you're almost certainly advised to check the Apache 
error.log file for specific problems. I guess you've read the following 
section of the documentation...

http://mercurial.selenic.com/wiki/PublishingRepositories#Allowing_push

Paul