501 error on push to https?

[Ted Pavlic]

It's just a hunch, but make sure all of your ErrorDocuments exist. In 
particular, make sure the error document for "File Not Found" (which, I 
think, is usually error 403, but it might be different over HTTPS) is 
present.

I had strange errors pushing to straight HTTP. After I made sure my 
error documents existed, everything started working.

--Ted

Ian Dees wrote:
> Hi, Andrew.
> 
>> I keep getting this:
>>
>> hg push
>> pushing to https://computer/hg/my-repo
>> abort: HTTP Error 501: Not Implemented
> 
> I've got the same problem with Apache running on Solaris at a shared
> host.  The common thread might be our non-default SSL certs: you're
> using a self-signed one, and I'm using a cheesy wildcard one from my
> host.
> 
> On the client side, I get a 501 on Windows, even just doing an hg
> clone from the https://... URL to my desktop.  The situation on OS X
> is much scarier: hg push prompts me for a user name and password (as
> it should), and then appears to send them _in the clear_ to the server
> over plain HTTP -- the response comes back, "ssl required."
> 
> Meanwhile, I can browse the repository just fine in any Web browser: I
> get properly warned about the certificate, my login is sent over
> HTTPS, and so on.
> 
> --Ian
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
> 

-- 
Ted Pavlic <ted at tedpavlic.com>