Hi.
I understand that the new FDSN web services return HTTP 204 to indicate no
data returned, and applaud this move.
If the service is temporarily not available (say because I've made too many
requests in parallel, system is busy, etc.) do I get a different return
code? If so, what?
Thanks!
-- John
I understand that the new FDSN web services return HTTP 204 to indicate no
data returned, and applaud this move.
If the service is temporarily not available (say because I've made too many
requests in parallel, system is busy, etc.) do I get a different return
code? If so, what?
Thanks!
-- John
-
Hi John
You might check this out, it has information on what codes are used when.
Not sure how closely the services hew to the spec, but...
http://www.fdsn.org/webservices/FDSN-WS-Specifications-1.0.pdf
I don't actually know, but my guess is that too many requests in parallel
would be silently killed by the load balancer/firewall thingy at the DMC as
the request would never actually make it to the web service itself. Would
be nice to have some official clarification so clients can avoid using too
many threads/sockets.
Philip
On Mon, Apr 15, 2013 at 6:01 PM, John D. West <john.d.west<at>asu.edu> wrote:
Hi.
I understand that the new FDSN web services return HTTP 204 to indicate no
data returned, and applaud this move.
If the service is temporarily not available (say because I've made too
many requests in parallel, system is busy, etc.) do I get a different
return code? If so, what?
Thanks!
-- John
_______________________________________________
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices
-
Hi John,
During some maintenance or error conditions you will receive an HTTP 503 when the service is unavailable.
For now, unfortunately, when you hit the limit of parallel requests the connections are dropped/reset at the TCP level. From the client perspective it would be better if we returned an HTTP 503 in this case. We'll look into making this possible and balance with other security implications.
Chad
----- Original Message -----
From: "John D. West" <john.d.west<at>asu.edu>
To: "IRIS Web Services List" <webservices<at>iris.washington.edu>
Sent: Monday, April 15, 2013 3:01:35 PM
Subject: [webservices] HTTP status code
Hi.
I understand that the new FDSN web services return HTTP 204 to indicate no data returned, and applaud this move.
If the service is temporarily not available (say because I've made too many requests in parallel, system is busy, etc.) do I get a different return code? If so, what?
Thanks!
-- John
_______________________________________________
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices