* Malcolm Wallace <[email protected]> [2013-04-09 08:40:51+0100] > > I still hope someone on this list can help me with my problem. > > Having 30s delay to hackage is rather annoying. > > Is the delay only to hackage? Or to many sites external to your company? > > Where I work, we found that our corporate proxy downloads and interprets > ~3000 lines of JavaScript on every web access, where the JavaScript consists > of a long series of regexp pattern-matches on the URL. Obviously if the site > you want is neither whitelisted nor blacklisted, it takes the longest time to > exhaust all the matches and drop through to the default case. > > Guess what? We have internal-only websites that are not on the whitelist, > and yes we see long delays to get to them too. > > I'm not saying your corporate IT is as bad as ours, but consider it as a > possibility. :-)
It is only to hackage. Also, this is a home ISP, and no proxy. 30 seconds is the time between: 1. I get a TCP ACK from hackage for my HTTP GET, and 2. I get the first packet with HTTP response from hackage. So, I am under a strong impression that this delay happens at hackage. The reason I thought this is a reverse DNS issue is that the servers which should provide reverse DNS for my ISP are (permanently) down, and an attempt to perform a reverse lookup results in a timeout (try "dig +trace -x 80.90.233.237"). Roman _______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
