W3C home > Mailing lists > Public > public-lod@w3.org > February 2017

Browsers breaking content negotiation

From: Martynas Jusevičius <martynas@graphity.org>
Date: Thu, 9 Feb 2017 19:32:29 +0100
Message-ID: <CAE35Vmw-2TLJ5Gwf6YMxSM0UxULitrC-Pei3D51_49UqdPEYAg@mail.gmail.com>
To: public-lod <public-lod@w3.org>, "public-rww@w3.org" <public-rww@w3.org>
Hey,

say I have such RDF data:

<http://some.com/img/abc.jpg> dct:format "image/jpeg" .

The URI also maps to an abc.jpg image file. This allows my Linked Data
platform to respond in at least 3 different ways to a request to such
URI, depending on the Accept request header:
1. the JPEG image for image/*
2. the RDF metadata for any RDF syntax
3. HTML rendering of the metadata for text/html

Yet recently I noticed that some browsers started sending Accept: */*
instead of image-specific media types:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation/List_of_default_Accept_values#Values_for_an_image
https://bugzilla.mozilla.org/show_bug.cgi?id=1249474

This provides no information for the content negotiation algorithm and
leading to a random response format. For example, the server would be
correct to return HTML, which is obviously not what the browser
expects.

Anyone else thinks such behavior breaks WWW architecture? Browser
vendors apparently have decided that conneg is bad:
https://wiki.whatwg.org/wiki/Why_not_conneg


Martynas
atomgraph.com
Received on Thursday, 9 February 2017 18:33:03 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 23 February 2017 16:49:10 UTC