W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2006

Re: HTTP Status Codes for QueryRequestRefused

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Tue, 10 Jan 2006 17:08:39 +0000
Message-ID: <43C3EA17.6060402@hp.com>
To: Kendall Clark <kendall@monkeyfist.com>
CC: RDF Data Access Working Group <public-rdf-dawg@w3.org>



Kendall Clark wrote:
> On Jan 10, 2006, at 8:17 AM, Seaborne, Andy wrote:
> 
> 
>>Kendall,
>>
>>Thnaks for finding that extract - it certainly helps me.
> 
> 
> Glad to hear it.
> 
> 
>>Given that faults are an open set, then we just need to be sure  
>>that the language of the SPARQL protocol is not providing a  
>>stronger condition.
> 
> 
> It doens't. It provides a *weaker* one, that is, a more specific one.  
> QueryRequestRefused *must* be returned *when* the service refuses to  
> process a request. Under no other condition does the must apply.

Example: service refuses a request because for a security access issue.

It would like to be more specific than 500, sending 403.

(From the client's point of view, I read "refuse" as covering all and any 
circumstances other than a bad request when a service is not going to execute 
a request.  "Unable" because of some issue like local security policy is a 
refusal).

	Andy

> 
> 
>>  It does do that for QueryRequestRefused where it places a "must"  
>>requirment (MalformedQuery only uses "should").
> 
> 
> Well, Malformed has two bits: you should return it but you *must* not  
> return a 2xx status code.
> 
> I sincerely don't see the problem you see.
> 
> Do you have any text you'd add to the spec in light of our  
> conversation and the WSDL quote about faults and open sets and the like?
> 
> Cheers,
> Kendall
Received on Tuesday, 10 January 2006 17:08:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:25 GMT