[JDEV] One more thing about OOB

[Peter Saint-Andre]

Hi Robert,

I poked Jer about the error messages, too. :) Again we might want to
look at RFC 2616 (ftp://ftp.isi.edu/in-notes/rfc2616.txt). Jer thought
401 sounded right but 502 didn't. If the recipient can't connect to the
URL, wouldn't we use 404? Maybe I'm misunderstanding exactly what you
mean by that scenario.

RFC 2616 defines 502 as follows....

******

10.5.3 502 Bad Gateway

   The server, while acting as a gateway or proxy, received an invalid
   response from the upstream server it accessed in attempting to
   fulfill the request.

******

Seems to me we'd probably want to stick close to the IETF standards
here, which say that:

   Response status codes beginning with the digit "5" indicate cases in
   which the server is aware that it has erred or is incapable of
   performing the request. 

It seems that by this scenario you mean something closer to 404, or
perhaps 503.

Best,

Peter

--
Peter Saint-Andre
stpeter at jabber.org

> Robert Temple wrote:
> 
> One more thing about OOB iqs.  We need to figure out standard error
> codes to use when a recipient is
> unable to get a file for some reason.  Right now I'm going to use 401
> Unauthorized if the recipient
> doesn't want to have the file sent to them.  And I'll use 502 Remote
> Server Error if I the recipient cannot
> connect to the URL that was sent though Jabber.
> 
> -Robert