W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > April 2011

HTTP status codes when no result is responded

From: Markus Luczak-Rösch <markus.luczak-roesch@fu-berlin.de>
Date: Fri, 01 Apr 2011 14:14:28 +0530
To: <public-rdf-dawg-comments@w3.org>
Message-ID: <C9BB8E44.7A87%markus.luczak-roesch@fu-berlin.de>
Hi all!

I recently sent a message to the public-LOD group where I got the pointer
to better place this here directly. I quickly went through the draft at
http://www.w3.org/2009/sparql/docs/protocol-1.1/ and found nothing about
the usage of HTTP status code 204, so I repeat my observation here:

Since on the LDOW11 and USEWOD workshops at WWW there was the recent
discussion about using HTTP referrers properly when browsing, crawling
etc. linked data (short using it) I would like to add another thing that I
was wondering about. If endpoints deliver no content to the client e.g. if
the client performs a SPARQL query that yields no results, servers answer
HTTP status code 200 and deliver some content that holds the information
that there were no results. As far as I see, there is the HTTP status code
204 for exactly this, isn't it? (see

So, beside the aforementioned and recently discussed proper usage of
referrers, I would also suggest to use the 204 HTTP status code.


Markus Luczak-Rösch (Dipl.-Inform.)| Freie Universität Berlin
Lecturer/Grad. Research Associate  | Dept. of Computer Science
Networked Information Systems WG   | Königin-Luise-Str. 24/26
                                   | D-14195 Berlin
www.ag-nbi.de                      | Phone: +49 30 838 75226
www.markus-luczak.de               | luczak@inf.fu-berlin.de
http://twitter.com/MLuczak         | Skype: markus_luczak
Received on Friday, 1 April 2011 08:42:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:01:28 UTC