X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E061BDA842; Tue, 22 Nov 2005 06:23:59 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 80216-02; Tue, 22 Nov 2005 10:24:00 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx-2.sollentuna.net (mx-2.sollentuna.net [195.84.163.199]) by svr1.postgresql.org (Postfix) with ESMTP id 575F7D7DB4; Tue, 22 Nov 2005 06:23:56 -0400 (AST) Received: from ALGOL.sollentuna.se (janus.sollentuna.se [62.65.68.67]) by mx-2.sollentuna.net (Postfix) with ESMTP id AF48C8F28A; Tue, 22 Nov 2005 11:23:58 +0100 (CET) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: Re: [HACKERS] Web page down (ad server) Date: Tue, 22 Nov 2005 11:23:58 +0100 Message-ID: <6BCB9D8A16AC4241919521715F4D8BCE6C7C27@algol.sollentuna.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [HACKERS] Web page down (ad server) thread-index: AcXvP+FmWLwe1Zn/R/WguQqiD5/lXgADtdwQ From: "Magnus Hagander" To: "Dennis Bjorklund" Cc: "Marc G. Fournier" , X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[AWL=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200511/137 X-Sequence-Number: 8852 > > > Turns out it's related to the ads, so if I just adblock the ad=20 > > > server I can see the page just fine. Kind of bad it's=20 > needed however=20 > > > :-) > > >=20 > > > I also tried to show the page in opera and it looks the=20 > same as in=20 > > > firefox. > >=20 > > Intersting. It works fine for me. Did you try multiple=20 > times? (Since=20 > > you tried a different browser, I assume you did). >=20 > Of course. Maybe it's was some dns problem (all the adresses=20 > seemed to resolve, but maybe some adress have been updated=20 > but not propagated to all dns servers, or something. What do I know?). >=20 > As I said, I could solve it just fine by using adblock so=20 > it's not a problem for me. I just wanted to tell someone about it. >=20 > I did try like 50 times during 30 minutes. Every time it got=20 > stuck waiting on 200.46.208.156. Aaahh. I missed that parto f your screenshot! That means ads.hub.org was down, and it would wait until it timed out. Marc - can we make that check async? Since you're updating the code anyway, because it breaks website XHTML complicancy? Need any help with the code? //Magnus