RE: [VM] bug in recipes ... fixes

OK, I found that IE6 sends the following Accept header with an HTTP GET request:

Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, application/x-shockwave-flash, */* 

Note that 'text/html', 'text/xml', 'application/xml', and 'application/xhtml+xml' are all absent.

I designed the conditional redirects in recipes 3, 4 & 5 (and also 8, 9 & 10) to work with the accept headers that Mozilla sends, assuming that IE would send similar headers, but I should have tested this.

Btw Mozilla sends the following Accept header:

Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5

What this means ... 

If we want the URIs of classes and properties to be 'clickable' (i.e. to take you to some human-friendly documentation when visited in a web browser) in both Mozilla and IE, then we have to turn recipes 3, 4 & 5 around, making HTML content the default response (i.e. what the client gets if it doesn't specify an 'Accept' header at all, or the 'Accept' header sent by the client is not recognised by the server), and requiring that clients send 'Accept: application/rdf+xml' if they want RDF/XML.

Changing the default response to HTML has obvious implications for RDF toolkits, as they would be forced to include an 'Accept: application/rdf+xml' header in all HTTP GET requests, which I believe they currently do not do (?)

And I thought I had been so clever!

So basically, if we want URIs to be clickable in IE, either we 

 (a) leave the recipes as they are and ask IE to send more headers, or 
 (b) change the recipes around and ask RDF toolkits to send more headers.

Cheers,

Al.

> -----Original Message-----
> From: public-swbp-wg-request@w3.org
> [mailto:public-swbp-wg-request@w3.org]On Behalf Of Miles, AJ 
> (Alistair)
> Sent: 17 January 2006 15:31
> To: public-swbp-wg@w3.org
> Subject: [VM] bug in recipes
> 
> 
> 
> Hi all,
> 
> BUG: I just noticed that the conditional redirects don't work 
> with IE6 as the client ... you always end up at the RDF 
> content. Anyone have an idea why? 
> 
> ---
> Alistair Miles
> Research Associate
> CCLRC - Rutherford Appleton Laboratory
> Building R1 Room 1.60
> Fermi Avenue
> Chilton
> Didcot
> Oxfordshire OX11 0QX
> United Kingdom
> Email:        a.j.miles@rl.ac.uk
> Tel: +44 (0)1235 445440
> 
> 
>

Received on Tuesday, 17 January 2006 16:04:21 UTC