Provide HTTP Headers in `HttpException`

[jmkeil]

Version

5.0.0

Feature

Hi. Currently, HttpExceptions thrown by QueryExecHTTP do not provide access to response headers. This prevents specific handling, like the consideration of Retry-After. I suggest to

• extend HttpException with a method getResponseHeaders() and an according constructor,
• extend QueryExceptionHTTP with a method getResponseHeaders() and an according constructor,
• provide the responses HttpHeaders instance during HttpException construction in HttpLib#handleHttpStatusCode or HttpLib#exception, and
• provide the responses HttpHeaders instance during QueryExceptionHTTP construction in QueryExceptionHTTP#rewrap.

Are you interested in contributing a solution yourself?

Perhaps?

[afs]

Hi @jmkeil ,

Seems reasonable. Another use is getting at header-carried request ids used for tracing.

It is exposing (a small part of) java.net.http at the API level. That said, it is possible to construct HttpHeaders standalone.

[jmkeil]

It is exposing (a small part of) java.net.http at the API level.

Instead of returning HttpHeaders itself, the multi map returned by HttpHeaders#map could be returned.

[afs]

It is exposing (a small part of) java.net.http at the API level.

Instead of returning HttpHeaders itself, the multi map returned by HttpHeaders#map could be returned.

True - but the afforance of multimaps is not great, while HttpHeaders has a clearly read-only API.

[jmkeil]

So HttpHeaders would be fine and preferred?

[jmkeil]

Thank you for solving this, @afs.