Re: dillo3-pre does not display images

----- Original Message -----
From: Jorge Arellano Cid <[email protected]>
To: [email protected]
Cc: 
Sent: Sunday, August 7, 2011 1:23 PM
Subject: Re: [Dillo-dev] dillo3-pre does not display images

On Sun, Aug 07, 2011 at 08:36:59AM -0700, Globe Trotter wrote:
> 
> 
> 
> ________________________________
> From: Axel Beckert <[email protected]>
> To: [email protected]
> Sent: Sunday, August 7, 2011 9:53 AM
> Subject: Re: [Dillo-dev] dillo3-pre does not display images
> 
> Hi,
> 
> On Sun, Aug 07, 2011 at 07:39:05AM -0700, Globe Trotter wrote:
> > Trying www.nytimes.com or www.huffingtonpost.com or
> > www.politico.com. While the frames are all messed up (as in Dillo
> > 2.2), now even the images do not get displayed.

  Images show here.

  Weird, I don't know what it may be...

  BTW, you have a preferences file full of non-dillo keywords (at
least not ours). Try:

    mv ~/.dillo/dillorc ~/.dillo/dillorc.BAK

  and see what hapopens by starting with the defaults

Thanks, Jorge. I have been using this file since the time I started using dillo.

Anyway, your suggested change did not produce any appreciable effect. 

$dillo
paths: Using /usr/local/etc/dillo/dillorc
paths: Using /usr/local/etc/dillo/keysrc
dillo_dns_init: Here we go! (threaded)
Enabling cookies as from cookiesrc...
Nav_open_url: new url='about:splash'
Nav_open_url: new url='http://www.dillo.org/'
Dns_server [0]: www.dillo.org is 134.102.206.165
Nav_open_url: new url='dpi:/bm/'
Nav_open_url: new url='http://www.nytimes.com'
Dns_server [0]: www.nytimes.com is 170.149.173.130
Connecting to 170.149.173.130
Capi_filters_test: DENY from 'www.nytimes.com' to 'css.nyt.com'

Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'ad.doubleclick.net'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: DENY from 'www.nytimes.com' to 'i1.nyt.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'www.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'graphics8.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'up.nytimes.com'
Capi_filters_test: ALLOW from 'www.nytimes.com' to 'wt.o.nytimes.com'
HTTP warning: 'http://www.nytimes.com/adx/bin/clientside/a06de63Q2Fomz6hZoiQ7C6ZKOQ7CV-miZQ25Q3C-EBmDmQ2BmQ25cQ2BBFF2hEDh' cannot be displayed as image; has media type 'text/html'
Dns_server [0]: graphics8.nytimes.com is 65.126.84.42 65.126.84.41
Dns_server [2]: wt.o.nytimes.com is 66.150.117.24
Dns_server [1]: up.nytimes.com is 107.20.222.53



Is this also what you get?

Someone wrote to me privately the following may work (though for Dillo 2.2.1). However, I am using dillo3-pre (on linux).


Offhand, I know some sites now use a trick called "lazy loading" where 
they default to a blank image, then load the "real" ones with 
JavaScript.  It's supposed to help page load times by forcing the text 
to load before images, but breaks non-JavaScript enabled browsers.

I've got a patch that works around one common version:
  http://dillo-win32.sourceforge.net/files/10-dillo-r1819.lazy_load.diff

What might also help is adding to your dillorc:
  http_user_agent="Mozilla/4.0 (compatible; Dillo 2.2.1)"

That
 tells sites that check your user agent to use simpler, Netscape 
4.x-friendly code, which is much closer to what Dillo currently 
supports.  I've made that the default in the Windows port, since sites 
like Google Images are almost completely unusable otherwise.

By 
the way, www.nytimes.com, www.huffingtonpost.com, and www.politico.com 
all work fine here -- I'm running dillo-win32-20110630 (more or less 
2.2.1 with some compatibility patches).


Thanks again!