tree b9e48667536097116f8cef73bdca5eaee912ab57
parent 16eaaff4e70c2fa0ca4d2d5b8447f661f5c3a138
author David Joaquim <david.joaquim@gmail.com> 1662116477 +0200
committer GitHub <noreply@github.com> 1662116477 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJjEeJ+CRBK7hj4Ov3rIwAAZzgIABzkSCszJJKEyf2AKHNvozhS
 gSwSj2RpWI9WCaGb5ot0gFgHCrTc8qDQo74QiG1lEV92kN3oLK1n83aWs3HWEaYW
 dHX11OD7HayWxWQAZU0FRktqm/15YFo15Vabhw+SLUtLtGS/h7UZh+KVJwHUtZQg
 cqgYCN6qYu00A4cFSyetMbNJt+xu89L2fqaWlKrzt0M6N7DP320RuXl5iz3LZQFT
 pEvDAkCpSV2PK5PqA34kHJyuz/2/lDRAZdo+31hIiBSPNsrkluQW385d1fQfH4OR
 P5pgKIwGpUObBT0cEwtgrFoR0KEM6gWXlxizEj6wWBS2xTv0ZFZqXMaNexCxLFE=
 =Mphq
 -----END PGP SIGNATURE-----
 

Change JettyConnector 'readTimeout' behavior to match socket read tim… (#5114)

* Change JettyConnector 'readTimeout' behavior to match socket read timeout definition - e.g., ApacheConnector behavior matches it.

* Read timeout: Time on waiting to receive the first data byte.

The `timeout` method timeouts the request even if data were already received, capping the query to a maximum execution time.
This behavior is problematic when streaming data over a prolonged duration; the client has already received data bytes, but data continues to flow.

I provided a jetty specific property (jersey.config.jetty.client.totalTimeout) that configures the 'totalTimeout' when required.