Comments on: What is your RDF browser’s Accept header?

By: Aftab Iqbal

Aftab Iqbal — Mon, 14 Jul 2008 10:02:17 +0000

Nice topic on Content Negotiation, it would really help a lot

By: Richard Cyganiak

Richard Cyganiak — Fri, 30 May 2008 08:07:25 +0000

Ian: The client just has to worry about sending an Accept header that matches its preferences and capabilities. The actual content negotiation, as well as the choice wether a redirect is sent, is always made by the server, so clients don’t really have to worry about it.

If you see only 200 response codes, then your client probably just doesn’t tell you about any redirects that were performed before it arrived at the final 200. See my little cURL tutorial for more information.

By: Ian Hebden

Ian Hebden — Fri, 30 May 2008 08:01:33 +0000

So, does that mean that if you use say the Disco style accept parameters, you will never get a 303 redirect? I’ve tried quite a few different URIs for non-information resources, and always get a status code of 200. In other words, if you use the Disco style, do you still need to worry about content negotiation, or is it done automaticaly?

By: Giovanni Tummarello

Giovanni Tummarello — Fri, 11 Apr 2008 20:57:16 +0000

:-)

By: Sergio Fernández

Sergio Fernández — Thu, 20 Mar 2008 22:26:21 +0000

You can also use EARL to generate the report ;-)

By: Richard Cyganiak

Richard Cyganiak — Tue, 18 Mar 2008 15:53:50 +0000

Laurens, Disco really sends that header.

By: Laurens Holst

Laurens Holst — Tue, 18 Mar 2008 14:49:29 +0000

In the Disco Hyperdata browser:

application/xml q=0.5

Is that a typo or does it actually send that?