On Fri, 20.02.15 14:23, Peter Paule (systemd-de...@fedux.org) wrote: > > Zitat von Lennart Poettering <lenn...@poettering.net>: > > >On Thu, 19.02.15 19:46, Peter Paule (systemd-de...@fedux.org) wrote: > > > >>BTW: > >> > >>--dkr-index-url cannot handle http redirects > >> > >>By accident I tried "http://index.docker.io"; and this will be redirected to > >>"https://index.docker.io"; but importd cannot handle this. > > > >I think this is actually a problem on the setup of the servers, not > >the client side. > > Look at this: > > % curl http://index.docker.io -I > HTTP/1.1 302 Found > Server: nginx/1.6.2 > Date: Fri, 20 Feb 2015 13:12:50 GMT > Content-Type: text/html > Content-Length: 160 > Location: https://index.docker.io/ > Connection: keep-alive > > If you try to get things from http://index.docker.io it will tell you, that > you > need to use https://index.docker.io/ instead. It might be questionable if 302 > really the best status code for this - maybe they should better use 301 for > this. So, yes looking at 301 and 302 it is a server problem somehow, but not > following 302 is kind of a client problem as well I think.
Hmm, I looked into this today, but this just worked for me now with git. Is this still broken for you? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
