img'es from funny redirecting urls aren't displayed
For example, opening a simple page with: <html> <body> <img src="http://imgur.com/N2XcD.png" /> </body> </html> ... the image is not displayed. Dillo simply says: Dns_server [0]: imgur.com is 72.251.206.98 BUT opening "dillo http://imgur.com/N2XcD.png" works: Dns_server [0]: imgur.com is 72.251.206.98 Connecting to 72.251.206.98 Nav_open_url: new url='http://i.imgur.com/N2XcD.png' Dns_server [0]: i.imgur.com is 208.122.28.2 208.122.28.3 208.122.28.4 208.122.28.10 208.122.28.11 208.122.28.12 208.122.28.13 208.122.28.18 208.122.28.20 208.122.28.21 208.122.28.26 208.122.28.27 208.122.28.29 208.122.28.30 Connecting to 208.122.28.2
On Wed, Feb 24, 2010 at 06:42:23PM -0500, Dennis Nezic wrote: Hi there, that's working as designed. (Unless the design has changed since I last looked.)
For example, opening a simple page with:
<html> <body> <img src="http://imgur.com/N2XcD.png" /> </body> </html>
... the image is not displayed. Dillo simply says:
Dns_server [0]: imgur.com is 72.251.206.98
The HTTP response is a 301 redirection. For images within a page, dillo doesn't follow them. (It was the case that enough redirected images were ads, trackers, or other probably-unwanted content. It likely still is the case.)
BUT opening "dillo http://imgur.com/N2XcD.png" works:
Dns_server [0]: imgur.com is 72.251.206.98 Connecting to 72.251.206.98 Nav_open_url: new url='http://i.imgur.com/N2XcD.png' Dns_server [0]: i.imgur.com is 208.122.28.2 208.122.28.3 208.122.28.4 208.122.28.10 208.122.28.11 208.122.28.12 208.122.28.13 208.122.28.18 208.122.28.20 208.122.28.21 208.122.28.26 208.122.28.27 208.122.28.29 208.122.28.30 Connecting to 208.122.28.2
It's still a HTTP 301 response, but here you requested the image url, and dillo does follow redirections for requested urls. f -- Francis Daly francis@daoine.org
Andreas wrote:
there is also
http://www.estofex.org/cgi-bin/polygon/showforecast.cgi?listvalid=yes
The map images on that page give a 30x redirect. If I select "isolate image", dillo sends GET /forecasts/tempmap/2010022606_201002241505_1_stormforecast.xml.png%20 HTTP/1.1
The Location: URL in the 30x HTTP-Header contains a trailing whitespace as an additional problem, Is dillo wrong here or is the server side wrong? Common sense says that spaces should be ignored.
Dillo is wrong. In RFC 2616, section 4.2: The field-content does not include any leading or trailing LWS: linear white space occurring before the first non-whitespace character of the field-value or after the last non-whitespace character of the field-value. Such leading or trailing LWS MAY be removed without changing the semantics of the field value. I'll fix this.
participants (4)
-
andreas＠kemnade.info -
corvid＠lavabit.com -
dennisn＠dennisn.dyndns.org -
francis＠daoine.org