International Federation of Digital Seismograph Networks

Thread: HTTP status 413 (Request Entity Too Large)

Started: Feb. 22, 2016, 2:30 p.m.
Last activity: Feb. 22, 2016, 2:30 p.m.
Joachim Saul
Feb. 22, 2016, 2:30 p.m.
Hello Working Group III,

fdsnws-dataselect sometimes responds with HTTP status 413 (Request
Entity Too Large). This requires reducing the request size by splitting
bulk requests into smaller pieces (fewer lines, possibly shorter time
windows) and submitting them separately.

It is clear that some limits are required in order to ensure operability
of the services. It is also clear that due to different implementations
and server capabilities at every fdsnws node the limits will have to be
node specific.

What is annoying from the user perspective is lack of a generic
mechanism to determine the server limits before submitting a request and
getting the 413 error. The returned error message text may contain a
description of the server limits but this is not mandatory.

The fdsnws specification 1.1 includes in table 1 with respect to error
413 the recommendation "Service limits should also be documented in the
service WADL." Even though this sounds like it could solve the problem
of unknown request limits, there is AFAICS no "official"
fdsnws-dataselect server where this feature has already been implemented.

Considering the usefulness especially in the context of federated data
centers, shouldn't the specification of server limits in the WADL be
made mandatory? Are there any plans in that direction?