--Original Message-
From: public-lod-requ...@w3.org [mailto:public-lod-requ...@w3.org] On Behalf Of
Andy Seaborne
Sent: Wednesday, April 27, 2011 5:35 AM
To: Hugh Glaser
Cc:
Subject: Re: Why does rdf-sparql-protocol say to return 500 when refusing a
query?
I agree with the sentiment. Teh HTTP st
y Seaborne
Sent: Wednesday, April 27, 2011 5:35 AM
To: Hugh Glaser
Cc:
Subject: Re: Why does rdf-sparql-protocol say to return 500 when refusing a
query?
I agree with the sentiment. Teh HTTP status codes jist aren't up to
this sort of work, they come from a background of accessing HTML pag
On 4/28/11 7:37 AM, Richard Cyganiak wrote:
On 28 Apr 2011, at 11:26, Leigh Dodds wrote:
However it may be useful to define a standard response format and
potentially error messages to help client apps/users distinguish
between more fine-grained error states. I suggested this during
discussion o
On 28 Apr 2011, at 11:26, Leigh Dodds wrote:
> However it may be useful to define a standard response format and
> potentially error messages to help client apps/users distinguish
> between more fine-grained error states. I suggested this during
> discussion of the original protocol specification b
Hi,
On 27 April 2011 11:18, Alexander Dutton wrote:
> On 17/04/11 21:07, Hugh Glaser wrote:
>>
>> As a consumer I would like to be able to distinguish a refusal to answer
>> from a failure of the web server to access the store, for example.
>
> In the general case, that was my concern, too. AFAIC
On Wed, 2011-04-27 at 09:14 +, Hugh Glaser wrote:
. . .
> 5xx is the server can't do what you want, and there isn't much point
> in the client having another go with the same request.
> However, as you say, it may be that the server could perform the
> request at another time.
The "Retry-After
On 17/04/11 21:07, Hugh Glaser wrote:
As a consumer I would like to be able to distinguish a refusal to answer from a
failure of the web server to access the store, for example.
In the general case, that was my concern, too. AFAICT from the spec, you
aren't precluded from returning e.g. 504 i
it's a legal
query).
Andy
On 17/04/11 21:07, Hugh Glaser wrote:
Ah, thanks.
That explains it.
I was puzzled why I was getting 500.
I assumed the endpoint was returning 500 by mistake.
Never crossed my mind it might be the the "correct" thing to do.
As a consumer I wou
>
>
> On 17/04/11 21:07, Hugh Glaser wrote:
>> Ah, thanks.
>> That explains it.
>> I was puzzled why I was getting 500.
>> I assumed the endpoint was returning 500 by mistake.
>> Never crossed my mind it might be the the "correct" thing to do.
>> A
puzzled why I was getting 500.
I assumed the endpoint was returning 500 by mistake.
Never crossed my mind it might be the the "correct" thing to do.
As a consumer I would like to be able to distinguish a refusal to answer from a
failure of the web server to access the store, for example
server to access the store, for example.
Best
Hugh
- Reply message -
From: "Alexander Dutton"
To: "public-lod"
Subject: Why does rdf-sparql-protocol say to return 500 when refusing a query?
Date: Sun, Apr 17, 2011 06:04
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
The SPARQL Protocol for RDF specification¹ say sin §2.2 that
"QueryRequestRefused [is] bound to HTTP status code 500 Internal
Server Error", and should be used "when a client submits a request
that the service refuses to process". The HTTP 1.
12 matches
Mail list logo
