On Mon, 2020-01-27 at 16:58 +0100, Tamás Cservenák wrote:
> Oleg,
>
> wire is "too much" for my use case.
>
> I basically want an "access log"-like log, but for upstream.
> so method, URL (so, full URL or at scheme + host + port + path) and
> roundtrip time
> (time elapsed when the response line
...also, I wanted to log ALL requests httpclient sends
So ended up with a LoggingRequestExecutor, something like this:
https://gist.github.com/cstamas/6a4165a64348490fa4fcdaa74757c966
but it looks to me like a hack. Also, unsure how to properly collect things
I need (ie. in case of proxy
Oleg,
wire is "too much" for my use case.
I basically want an "access log"-like log, but for upstream.
so method, URL (so, full URL or at scheme + host + port + path) and
roundtrip time
(time elapsed when the response line arrived). so to say like "access log"
but on client side.
This log will
On Mon, 2020-01-27 at 14:14 +0100, Tamás Cservenák wrote:
> Howdy,
>
> I'd like to log ANY remote request httpClient 4.5.x does (stable),
> what is
> the best way to active that? (like "upstream" request log, so method
> + URL
> [schema://hostname/path]).
>
> I'd like to cover cases even like
Howdy,
I'd like to log ANY remote request httpClient 4.5.x does (stable), what is
the best way to active that? (like "upstream" request log, so method + URL
[schema://hostname/path]).
I'd like to cover cases even like httpClient CONNECT requests, httpClient
retries (if configured to do so) and
The Apache HttpComponents project is pleased to announce 5.0-beta7
release of HttpComponents Client.
This BETA release upgrades HttpCore to the latest version and
addresses a number of issues found since the previous BETA release.
Notable changes and features in the 5.0 series:
