Re: how browsers transform URLs

This is really cool.

I'm assuming that the yellow highlights indicate cases where implementations differ, correct? 

AIUI you're testing both IMG tags and HTML forms, but I only see one set of results for each browser/os/test case combination. Did you not see any differentiation?

Also, what about A tags and other means of generating links?

Cheers,

P.S. in the design document under "Test page generation", you have an unescaped <img> tag.


On 26/11/2009, at 6:49 AM, Erik van der Poel wrote:

> We are happy to announce the open source release of Client URL
> Internet Emission Sniffer (CURLIES).
> 
> The purpose of this project is to see how browsers and other Web
> clients transform URLs as they access them. This is done by generating
> a number of test cases and having each client load the test files
> while running a packet sniffer to capture the network emissions.
> Reports are then generated from the sniffed packets, highlighting
> differences between the clients. For further details and test results,
> see the project site:
> 
> http://code.google.com/p/curlies/
> http://code.google.com/p/curlies/wiki/DesignDocumentForClientURLInternetEmissionSniffer
> 
> I have also written some recommendations for browser developers. While
> the HTML5 Web Addresses spec already describes how to parse and
> resolve a URL, I have taken this a step further to include the DOM
> interfaces that can be used to obtain IRIs, URIs and Unicode host
> names.
> 
> http://code.google.com/p/curlies/wiki/RecommendationsForBrowserDevelopers
> http://www.w3.org/html/wg/href/draft
> 
> Happy Thanksgiving!
> 
> Erik
> 
> PS Many thanks to Shaopeng Jia (Google), who did most of the actual work.
> 


--
Mark Nottingham     http://www.mnot.net/

Received on Wednesday, 23 December 2009 00:08:57 UTC