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

Re: HTTP Status Codes for QueryRequestRefused

From: Kendall Clark <kendall@monkeyfist.com>
Date: Tue, 10 Jan 2006 12:20:51 -0500
Message-Id: <96BA6010-8D09-4EB4-8359-87F630C0F5ED@monkeyfist.com>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>
To: andy.seaborne@hp.com


On Jan 10, 2006, at 12:08 PM, Seaborne, Andy wrote:

> (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).

Hmm, okay, then that's the bit we need to tweak. I have understood  
all along -- especially given the other bit which you never quote or  
seem to acknowledge: "The QueryRequestRefused fault message does not  
indicate whether the server may or may not process a subsequent,  
identical request or requests." -- that QueryRequestRefused is for  
policy refusals, not for anything else.

In yr example, WSDL faults are an open set, and the usual or ordinary  
HTTP status code for security issue (403 perhpas?) is perfectly legal  
to return. Honestly, Andy, let's find some other way to fix this  
because I have no more confidence that I'm going to convince you than  
you probably have of convincing me. Or, put another way, I'm very  
unlikely to be convinced of yr position, at least not w/out something  
new.

Would making the "refusal for reasons of policy" more explicit help you?

Cheers,
Kendall
--
You're part of the human race
All of the stars and the outer space
Part of the system again
Received on Tuesday, 10 January 2006 17:21:03 GMT

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