Registry returns HTTP 400 after exception, rather than 500, when metadata can't be parsed

18811
Reporter: mblissett
Type: Bug
Summary: Registry returns HTTP 400 after exception, rather than 500, when metadata can't be parsed
Priority: Minor
Resolution: Fixed
Status: Closed
Created: 2016-11-17 20:44:11.243
Updated: 2016-12-05 14:35:48.363
Resolved: 2016-12-05 14:35:48.228
        
Description: http://api.gbif.org/v1/dataset/9d1faf2a-1383-43a3-9862-2d5028eca053

This has invalid metadata, see http://data.nina.no:8080/ipt/eml.do?r=transforest&v=1.0 which has ", , , ," in the userId element.

The metadata needs to be fixed, but the registry should return an error response, rather than 400 Bad Request, which doesn't stand out in the logs.

See http://elk.gbif.org:5601/goto/a780105c6838671e5c33e25bf5c1d292 -- there are a lot of these.
]]>
    

Author: cgendreau
Comment: "directory" is parsed as an URI and the IllegalArgumentException was not caught so Jersey returned a 400.
Created: 2016-11-18 12:12:27.432
Updated: 2016-11-18 12:16:59.423