[gcs-pcs-list] new issue: is 406 correct?

[Daniel Chudnov]

As of yet we're at +2 on this, with no additional comments.  That so
few have weighed in could be because nobody cares, or because it's a
trivial change, or because it's complicated, or because people are busy
doing work they get paid for...  I dunno.  

In the past we've typically gotten at least five votes within 24 hours,
so I'm raising a special flag on this.  I'm hesitant to make a spec
change without at least a +5-or-so tally.  If you haven't had a chance to
review this, please take a moment to do so.  If you're indifferent, please
say so.  Even +2 and 3 indifferents/abstensions is better than just +2. :)

I'll leave it open over the weekend, but will start another issue/vote
thread in the meantime.

Thanks, -Dan


Daniel Chudnov wrote, on Thu, Mar 02, 2006 at 03:14:31PM -0500:
> unAPI revision 1 states, at the very bottom, among the HTTP status
> code notes:
> 
>   "requests for a URI that is available on the server but for a format
>   that is not available for that URI should return status code 406
>   Not Acceptable"
> 
> 
> While implementing OPA I reread what HTTP status code 406 Not Acceptable
> means:
> 
>   http://rfc.net/rfc2616.html#s10.4.7
> 
>   "The resource identified by the request is only capable of generating
>   response entities which have content characteristics not acceptable
>   according to the accept headers sent in the request."
> 
> Note that we are not currently addressing accept headers in unAPI 
> (not that it hasn't come up :).
> 
> Perhaps it would be better to use HTTP 415 Unsupported Media Type:
> 
>   http://rfc.net/rfc2616.html#s10.4.16
> 
>   "The server is refusing to service the request because the entity of
>   the request is in a format not supported by the requested resource
>   for the requested method."
> 
>   (Note that this does not even specify mime-type but rather the more
>    general-purpose "format".)
> 
> 
> That seems like an exact match, and therefore better.  I'll propose we
> change that note, and thus the spec, to now read (where before it read
> as in the first quote):
> 
>   "requests for a URI that is available on the server but for a format
>   that is not available for that URI should return status code 415
>   Unsupported Media Type"
> 
> 
> But, I have no idea if this matters to browsers/languages/etc.
> 
>   -Dan
> 
> 
> -- 
> Daniel Chudnov
> Yale Center for Medical Informatics
> (203) 737-5789
> _______________________________________________
> gcs-pcs-list mailing list
> gcs-pcs-list at cipolo.med.yale.edu
> http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list
> 

-- 
Daniel Chudnov
Yale Center for Medical Informatics
(203) 737-5789