[Edbrowse-dev] Acid3 test fails to start

[Edbrowse-dev] Acid3 test fails to start

[Karl Dahlke]

[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]

I received this message through github.

>From Vitaly Shukela

Acid3 fails to start. I wanted to check how much points will edbrowse get,
but there is no number at all: *$ ./src/edbrowse http://acid3.acidtests.org/
183856
warning: http error 404, Not Found
line 153: could not fetch javascript from http://acid3.acidtests.org/data:text/javascript,d1%20%3D%20'one'%3B, code 404
warning: http error 404, Not Found
line 154: could not fetch javascript from http://acid3.acidtests.org/data:text/javascript;base64,ZDIgPSAndHdvJzs%3D, code 404
warning: http error 404, Not Found
line 155: could not fetch javascript from http://acid3.acidtests.org/data:text/javascript;base64,%5a%44%4d%67%50%53%41%6e%64%47%68%79%5a%57%55%6e%4f%77%3D%3D, code 404
And more like this.

The javascript does not fetch, and I'm seeing this on more and more sites.
Others report same.
We can't parse the javascript if we can't even fetch it.
All these websites can't be misconfigured.
There is some problem with the mechanism of pulling down the file,
or interpreting the url, or some such.
I tried to fetch this file many different ways,
but can't seem to pull it down at all, in any way.
Any ideas??

I think if this case was solve, many other websites
would fetch their javascript properly as well.

Karl Dahlke

Re: [Edbrowse-dev] Acid3 test fails to start

[Adam Thompson]

[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]

On Wed, Jan 21, 2015 at 06:25:10PM -0500, Karl Dahlke wrote:
> I received this message through github.
> 
> From Vitaly Shukela
> 
> Acid3 fails to start. I wanted to check how much points will edbrowse get,
> but there is no number at all: *$ ./src/edbrowse http://acid3.acidtests.org/
> 183856
> warning: http error 404, Not Found
> line 153: could not fetch javascript from http://acid3.acidtests.org/data:text/javascript,d1%20%3D%20'one'%3B, code 404
> warning: http error 404, Not Found
> line 154: could not fetch javascript from http://acid3.acidtests.org/data:text/javascript;base64,ZDIgPSAndHdvJzs%3D, code 404
> warning: http error 404, Not Found
> line 155: could not fetch javascript from http://acid3.acidtests.org/data:text/javascript;base64,%5a%44%4d%67%50%53%41%6e%64%47%68%79%5a%57%55%6e%4f%77%3D%3D, code 404
> And more like this.
> 
> The javascript does not fetch, and I'm seeing this on more and more sites.
> Others report same.
> We can't parse the javascript if we can't even fetch it.
> All these websites can't be misconfigured.
> There is some problem with the mechanism of pulling down the file,
> or interpreting the url, or some such.
> I tried to fetch this file many different ways,
> but can't seem to pull it down at all, in any way.
> Any ideas??
> 
> I think if this case was solve, many other websites
> would fetch their javascript properly as well.

Ok, after looking at the site's source and doing a bit of research apparently they're using the inline data uri scheme:
http://en.wikipedia.org/wiki/Data_URI_scheme

What this basically means is that the data is in the src attribute and we
somehow need to fake fetch this. I've got no idea how to implement this,
but it looks to be increasingly common,
probably because it allows the web page to contain multiple different files,
all downloaded as one large chunk.
In the case of these tests, I suspect it's being used to simulate sourcing
scripts from elsewhere, though why you'd do things like this with javascript in
anywhere than a test suite I'm not sure.
As for other sites, I've seen a number of 404 errors,
some of which appear to be because multiple versions of a script are being used
and one is actually being fetched (I assume most browsers hide the 404 errors
for the others or we're not running the browser detection code correctly).

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]