I accidentally sent this URL to the event service. PREF is not a valid
catalog I know, but the service seemed to simply close the connection
rather than sending back a http error code, which makes it harder to debug
bad queries.
http://service.iris.edu/fdsnws/event/1/query?&minmag=5.0&maxmag=10.0&catalog=PREF&starttime=2012-04-01T00:00:00.000&endtime=2013-04-02T19:43:34.445
Deleting the "&catalog=PREF", or changing it to NEIC+PDE results in a valid
query with events.
For comparison, if I change the starttime to be a bad date like
32012-04-01T00:00:00.000
I get back a "Error 400: Bad date value for starttime:
32012-04-01T00:00:00.000" which is helpful in figuring out what I did wrong.
thanks
Philip
catalog I know, but the service seemed to simply close the connection
rather than sending back a http error code, which makes it harder to debug
bad queries.
http://service.iris.edu/fdsnws/event/1/query?&minmag=5.0&maxmag=10.0&catalog=PREF&starttime=2012-04-01T00:00:00.000&endtime=2013-04-02T19:43:34.445
Deleting the "&catalog=PREF", or changing it to NEIC+PDE results in a valid
query with events.
For comparison, if I change the starttime to be a bad date like
32012-04-01T00:00:00.000
I get back a "Error 400: Bad date value for starttime:
32012-04-01T00:00:00.000" which is helpful in figuring out what I did wrong.
thanks
Philip
-
Hi Philip,
Thanks, we'll file this as a feature request. It makes that we should be able to check for a known catalog name.
Chad
On Apr 2, 2013, at 12:55 PM, Philip Crotwell <crotwell<at>seis.sc.edu> wrote:
I accidentally sent this URL to the event service. PREF is not a valid catalog I know, but the service seemed to simply close the connection rather than sending back a http error code, which makes it harder to debug bad queries.
http://service.iris.edu/fdsnws/event/1/query?&minmag=5.0&maxmag=10.0&catalog=PREF&starttime=2012-04-01T00:00:00.000&endtime=2013-04-02T19:43:34.445
Deleting the "&catalog=PREF", or changing it to NEIC+PDE results in a valid query with events.
For comparison, if I change the starttime to be a bad date like
32012-04-01T00:00:00.000
I get back a "Error 400: Bad date value for starttime: 32012-04-01T00:00:00.000" which is helpful in figuring out what I did wrong.
thanks
Philip
_______________________________________________
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices
-
Never mind, this might be me not catching the 204. Thought I was, but not
so.
Philip
On Tue, Apr 2, 2013 at 3:55 PM, Philip Crotwell <crotwell<at>seis.sc.edu>wrote:
I accidentally sent this URL to the event service. PREF is not a valid
catalog I know, but the service seemed to simply close the connection
rather than sending back a http error code, which makes it harder to debug
bad queries.
http://service.iris.edu/fdsnws/event/1/query?&minmag=5.0&maxmag=10.0&catalog=PREF&starttime=2012-04-01T00:00:00.000&endtime=2013-04-02T19:43:34.445
Deleting the "&catalog=PREF", or changing it to NEIC+PDE results in a
valid query with events.
For comparison, if I change the starttime to be a bad date like
32012-04-01T00:00:00.000
I get back a "Error 400: Bad date value for starttime:
32012-04-01T00:00:00.000" which is helpful in figuring out what I did wrong.
thanks
Philip