• A/C (unregistered)

    Ah, 2008, the early REST days. :-)

    Essentially, if the report was being dynamically generated and the request was idempotent, the appropriate method would have been (and largely, still is) GET.

    There is no mention of server or for that matter even client limits being exceeded, and as correctly mentioned, the RFC did not at the time and still does not put any specific limit on the maximum length of a URI (which would be of necessity arbitrary and not very future-proof).

    In other words, the developers were doing it right and likely knew what they were doing.

    Long URIs are no longer uncommon in these REST API dominated days (data:// URIs anyone?) so I guess the last laugh is on those developers.

Leave a comment on “HTTP 414: Way Too F#%&ing Long”

Log In or post as a guest

Replying to comment #:

« Return to Article