JCL-402: Low-level client throws enriched exceptions by NSeydoux · Pull Request #1157 · inrupt/solid-client-java
marked this pull request as ready for review
NSeydoux
changed the base branch from
JCL-460/problem-details-class
to
JCL-402/problem-details-exceptions
NSeydoux
changed the title
JCL-463: Low-level client throws enriched exceptions
JCL-402: Low-level client throws enriched exceptions
NSeydoux
marked this pull request as ready for review
NSeydoux
changed the base branch from
JCL-402/problem-details-exceptions
to
JCL-460/problem-details-class-http-status
Base automatically changed from JCL-460/problem-details-class-http-status to main
April 18, 2024 11:53
`SolidClient` now parses HTTP error responses if they are compliant with RFC9457 in order to throw a structured exception. In case when no JSON parser is available in the classpath, the default behavior is to build a ProblemDetails object that only relies on the data available in the HTTP response status code.
It will be used in Jena and RDF4J modules too
HTTP body handlers are applied by the low-level HTTP client, so they should only ever map to an HTTP response. The processing of that response is then the responsibility of the caller.
NSeydoux
deleted the
JCL-463/solid-client-throws-pd-exception
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters