On Friday, 13 September 2013 at 07:30:36 UTC, Sönke Ludwig wrote:
Sorry for that. It was introduced by my workaround for the GZIP issue. Works again now. I'll look into a proper fix today.


Am 13.09.2013 08:41, schrieb Mathias Lang:
Same here with chromium on a win7 64.


2013/9/13 growler <growler...@gmail.com <mailto:growler...@gmail.com>>

On Friday, 13 September 2013 at 00:56:27 UTC, Craig Dillabaugh wrote:

On Thursday, 12 September 2013 at 21:30:38 UTC, Craig Dillabaugh
       wrote:

On Thursday, 12 September 2013 at 21:06:22 UTC, Kapps wrote:

On Thursday, 12 September 2013 at 18:01:43 UTC, Craig
               Dillabaugh wrote:


Currently any attempt to access the precompiled
                   binaries, eg:

http://code.dlang.org/files/__dub-0.9.18-linux-x86_64.tar.gz <http://code.dlang.org/files/dub-0.9.18-linux-x86_64.tar.gz>

                   returns

                   500 - Internal Server Error.

                   Internal error information:
object.Exception@../../../opt/__vibe/source/vibe/inet/message.__d(352):
                   Enforcement failed
                   ----------------
                   ./dub-registry(pure @safe bool
std.exception.enforce!(bool).__enforce(bool, lazy
                   const(char)[],
                   immutable(char)[], ulong)+0x6b) [0x5e31ab]
                   ./dub-registry(void
vibe.inet.message.__InetHeaderMap.remove(__immutable(char)[])+0x182)
                   [0x744dfa]
                   ./dub-registry(void
vibe.http.fileserver.sendFile(__vibe.http.server.__HTTPServerRequest,
                   ...


Try a different browser. I had this issue when using
               curl / wget, but it worked with Firefox.


Failed with Firefox, Opera, and Chromium. Maybe it is something
           with my PC, will try again from another PC.


Same problem with Opera/Chrome from my home PC (Windows 7). My previous attempts were from my Linux machine at the office where
       I tried Firefox/Opera/Chromium.

       I am the only one experiencing this?

       Craig


   I'm getting this also on a windows PC from a Chrome browser.

Thanks.  Works for me now.

Reply via email to