Bug#558125: epiphany-browser - Caches the decision to use ipv6 over network topology changes

[Simon Paillard]

Hi,

On Mon, Mar 29, 2010 at 10:20:38AM +0200, Julien Cristau wrote:
> On Mon, Mar  8, 2010 at 09:58:18 -0300, Gustavo Noronha Silva wrote:
> > On Sat, 2010-03-06 at 14:03 +0100, Julien Cristau wrote:
> > > I seem to be seeing this too.  Trying to connect to www.google.com right
> > > now results in a connect() to 2a00:1450:8007::93, which fails with
> > > ENETUNREACH, and epiphany immediately returns an error page instead of
> > > trying one of the other addresses.  Looks like it's not actually caching
> > > ipv4 vs ipv6, but just one ip address for the url…
> > 
> > This is likely a problem in libsoup, or on GResolver. I'll ask Dan
> > Winship.
>
> Any luck?

(Re-Ping)

As I met this again in the context of Debian WWW mirrors (one mirror removed
from the DNS rotation with little enough TTL), but epiphany still tried to
connect to an outdated IP.

So basically it behaves as if we had a infinite TTL: breaking redundancy, load
balancing..

I'm not used enough to gdb, so cannot locate/provide patch, but here are some
results/conclusions (on squeeze and sid):

- unless a DNS request fails for a host, then further requests for that uri
  (example on force refresh) will be performed against 0x00 host (epiphany
  really wants to know about root servers ?) 
- *each time the mouse is moved*, a DNS request is performed for the uri for the
  DOM object (so 0x00 for the background/already resolved, host for the link) !!

_ephy_web_view_hook_into_links ?


-- 
Simon Paillard