Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.003 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'responding': 0.07; 'stack.': 0.07; 'blocking': 0.09; 'tcp/ip': 0.09; 'bug': 0.10; "wouldn't": 0.11; '"connection': 0.16; 'bug,': 0.16; 'connect.': 0.16; 'ipv6': 0.16; 'port"': 0.16; "shouldn't": 0.17; 'help.': 0.22; "i'd": 0.22; 'this:': 0.23; 'installed': 0.23; 'to:2**1': 0.23; 'header:In-Reply-To:1': 0.25; 'header:User-Agent:1': 0.26; 'wondering': 0.26; 'firewall': 0.29; 'case,': 0.29; 'probably': 0.29; "i'm": 0.29; 'figure': 0.30; 'problem.': 0.32; 'to:addr :python-list': 0.33; 'server': 0.35; 'problem,': 0.35; 'but': 0.36; 'subject:: ': 0.38; 'to:addr:python.org': 0.39; 'takes': 0.39; 'received:192': 0.39; 'received:192.168': 0.40; 'your': 0.60; 'more': 0.63; 'received:204': 0.72 Date: Wed, 17 Oct 2012 11:58:23 +0200 From: Laszlo Nagy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: Hans Mulder , python-list@python.org Subject: Re: bad httplib latency due to IPv6 use References: <1s42l9-9al.ln1@satorlaser.homedns.org> <507e7c43$0$6845$e4fe514c@news2.news.xs4all.nl> In-Reply-To: <507e7c43$0$6845$e4fe514c@news2.news.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 11 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1350468497 news.xs4all.nl 6871 [2001:888:2000:d::a6]:35558 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:31492 >> What I'm wondering is this: >> 1. The server only serves on IPv4, changing this to IPv6 would probably >> help. However, I wouldn't consider this a bug, or? > I'd say it's a bug in your TCP/IP stack. An IP shouldn't take that long > to figure out that it is not configured to connect to IPv6 addresses. It might also be, that he has a firewall installed that is blocking access to ::1. In that case, it takes much more time to figure out that you cannot connect. Because in that case, it is not a "connection refused" problem, but a "trying to connect to a closed/not responding port" problem.