Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] https (HTTP/1.1) request timeout

Hi Simone,

Many thanks for the quick and nice response. It is clear now. 

Best Regards,

-----Original Message-----
From: jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx] On Behalf Of Simone Bordet
Sent: 2018年5月14日 17:01
To: JETTY user mailing list <jetty-users@xxxxxxxxxxx>
Subject: Re: [jetty-users] https (HTTP/1.1) request timeout


On Mon, May 14, 2018 at 10:50 AM, Cao, William (NSB - CN/Qingdao) <william.cao@xxxxxxxxxxxxxxx> wrote:
> I am trying to use Jetty client (9.4.7 and 9.2.24) to develop a https 
> client (HTTP/1.1). When it tried to send out the request, the server 
> can receive the request and respond it, and in the client side the 
> jetty log also shows that it got 200 OK response. However, the client 
> application got timeout. I think the major point is the 
> onContent(Response response, ByteBuffer buffer, Callback callback), 
> and we can call callback.succeeded() to terminate the onContent(…). 
> How should I check that all the content is received so that I can call callback.succeeded() in onContent(…) so as to avoid the timeout?

onContent(...) may be called multiple times.
Every time you must call callback.succeeded() to signal that you have processed the content and that you want to get the next content chunk.

Simone Bordet
Developer advice, training, services and support from the Jetty & CometD experts.
jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top