On Mon, 25 Jun 2012, David Euresti wrote:
> So it turns out it has to do with redirecting http to https and the
> downloader is actually trying to read the encrypted data. We're working
> on a workaround that won't redirect to https so that the current code
> will work. And we'll also put out a new package that will fix the
> problem soon. Sorry about that.
Weird, I tried to patch the wrapper to download directly using https URL
but this doesn't seem to help.
And strangely using https URL directly with curl returns 404 errors?
On Mon, 25 Jun 2012, David Euresti wrote:
> So it turns out it has to do with redirecting http to https and the
> downloader is actually trying to read the encrypted data. We're working
> on a workaround that won't redirect to https so that the current code
> will work. And we'll also put out a new package that will fix the
> problem soon. Sorry about that.
Weird, I tried to patch the wrapper to download directly using https URL
but this doesn't seem to help.
And strangely using https URL directly with curl returns 404 errors?
$ curl -I https:/ /www.dropbox. com/download? plat=x86 yMDQ2OTUyOTI0Mj Q0MjgyMTgyMTk2N TA4MTczNjYy; expires=Sat, 24-Jun-2017 20:07:06 GMT; Path=/; httponly
HTTP/1.1 404 NOT FOUND
Server: nginx/1.0.14
Date: Mon, 25 Jun 2012 20:07:06 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
set-cookie: gvc=MTIzNzE2MTE
x-frame-options: SAMEORIGIN
pragma: no-cache
cache-control: no-cache
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Get the Debian Administrator's Handbook: debian- handbook. info/get/
→ http://