HttpErrorResponseInterceptor does not handle 405 errors well

12564
Reporter: lfrancke
Type: Improvement
Summary: HttpErrorResponseInterceptor does not handle 405 errors well
Priority: Minor
Resolution: Fixed
Status: Closed
Created: 2012-12-20 17:36:45.364
Updated: 2013-12-06 13:57:56.278
Resolved: 2013-12-06 13:57:56.245
        
Description: There is no meaningful stacktrace or error message on a 405 response code.

only

{quote}
rg.gbif.ws.client.interceptor.HttpErrorResponseInterceptor$FullUniformInterfaceException:
    at org.gbif.ws.client.interceptor.HttpErrorResponseInterceptor.invoke(HttpErrorResponseInterceptor.java:59) ~[crawler.jar:na]
{quote}]]>
    

Author: mdoering@gbif.org
Comment: what would you expect, converting it into a NoSuchMethodException or some other exception? Or just see "HTTP 405"?
Created: 2012-12-20 23:10:10.806
Updated: 2012-12-20 23:10:10.806

Author: lfrancke@gbif.org
Comment: Yeah for all these errors that are not mapped I need to at least see which response code I got.
Created: 2012-12-20 23:20:10.1
Updated: 2012-12-20 23:20:10.1

Author: mdoering@gbif.org
Comment: http://code.google.com/p/gbif-common-resources/source/detail?r=1241
Created: 2012-12-20 23:32:14.146
Updated: 2012-12-20 23:32:14.146

Author: lfrancke@gbif.org
Comment: Sweet! Thanks!
Created: 2012-12-21 11:47:54.539
Updated: 2012-12-21 11:47:54.539

Author: fmendez@gbif.org
Comment: This issue was fixed by a commit mentioned in related comment
Created: 2013-12-06 13:57:56.275
Updated: 2013-12-06 13:57:56.275