git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* git clone over HTTP returns 500 on invalid host name
@ 2012-06-13 23:36 Shawn Pearce
  2012-06-13 23:40 ` Junio C Hamano
  0 siblings, 1 reply; 3+ messages in thread
From: Shawn Pearce @ 2012-06-13 23:36 UTC (permalink / raw)
  To: git

$ git clone https://this.host.does.not.exist/foo
Cloning into 'foo'...
error: The requested URL returned error: 500 while accessing
http://this.host.does.not.exist/foo/info/refs
fatal: HTTP request failed


Hmm. Telling me the host doesn't exist is more useful than 500:

$ git clone git://this.host.does.not.exist/foo
Cloning into 'foo'...
fatal: Unable to look up this.host.does.not.exist (port 9418) (Name or
service not known)


Does anyone care about this other than me?  :-)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: git clone over HTTP returns 500 on invalid host name
  2012-06-13 23:36 git clone over HTTP returns 500 on invalid host name Shawn Pearce
@ 2012-06-13 23:40 ` Junio C Hamano
  2012-06-13 23:43   ` Shawn Pearce
  0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2012-06-13 23:40 UTC (permalink / raw)
  To: Shawn Pearce; +Cc: git

Shawn Pearce <spearce@spearce.org> writes:

> $ git clone https://this.host.does.not.exist/foo
> Cloning into 'foo'...
> error: The requested URL returned error: 500 while accessing
> http://this.host.does.not.exist/foo/info/refs
> fatal: HTTP request failed
>
>
> Hmm. Telling me the host doesn't exist is more useful than 500:
>
> $ git clone git://this.host.does.not.exist/foo
> Cloning into 'foo'...
> fatal: Unable to look up this.host.does.not.exist (port 9418) (Name or
> service not known)
>
>
> Does anyone care about this other than me?  :-)


$ git clone https://this.host.does.not.exist/foo
Cloning into 'foo'...
error: Couldn't resolve host 'this.host.does.not.exist' while accessing https://this.host.does.not.exist/foo/info/refs
fatal: HTTP request failed

What are we doing differently?  Perhaps you have a custom proxy that
throws 500 back at you or something?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: git clone over HTTP returns 500 on invalid host name
  2012-06-13 23:40 ` Junio C Hamano
@ 2012-06-13 23:43   ` Shawn Pearce
  0 siblings, 0 replies; 3+ messages in thread
From: Shawn Pearce @ 2012-06-13 23:43 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: git

On Wed, Jun 13, 2012 at 4:40 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Shawn Pearce <spearce@spearce.org> writes:
>
>> $ git clone https://this.host.does.not.exist/foo
>> Cloning into 'foo'...
>> error: The requested URL returned error: 500 while accessing
>> http://this.host.does.not.exist/foo/info/refs
>> fatal: HTTP request failed
>>
>>
>> Hmm. Telling me the host doesn't exist is more useful than 500:
>>
>> $ git clone git://this.host.does.not.exist/foo
>> Cloning into 'foo'...
>> fatal: Unable to look up this.host.does.not.exist (port 9418) (Name or
>> service not known)
>>
>>
>> Does anyone care about this other than me?  :-)
>
>
> $ git clone https://this.host.does.not.exist/foo
> Cloning into 'foo'...
> error: Couldn't resolve host 'this.host.does.not.exist' while accessing https://this.host.does.not.exist/foo/info/refs
> fatal: HTTP request failed
>
> What are we doing differently?  Perhaps you have a custom proxy that
> throws 500 back at you or something?

Grrr. Yes. Its the contrib/persistent-https proxy that is causing
this, and a url.insteadof in ~/.gitconfig that always uses it for
https:

  [url "persistent-https://"]
    insteadof = https://

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-06-13 23:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-13 23:36 git clone over HTTP returns 500 on invalid host name Shawn Pearce
2012-06-13 23:40 ` Junio C Hamano
2012-06-13 23:43   ` Shawn Pearce

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).