Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty SSL port does not close even maxIdleTime is reached

If you want answers quicker, provide better context.

What OS were you using?
What was the OS configuration?
What was your network configuration?
What was your Client configuration?
What was your Server configuration?
Since hping2 is not a first party application, you could have said "I was using hping2 from ___ version _____, with the following command: $ hping2 ______"
Since you mentioned SSL, you could have also mentioned your SSL configuration on the server side? or the client side (hping2)?
Since you are using Jetty, you could have included "I am using Jetty version ____, started with Java version ____, using the following Jetty configuration: _____"
You have made no mention of what steps you have done to gather the information you reported?

You will have a much more pleasant experience if you provide useful information up front and don't rely on others to have to pull that information out of you with dozens of followup questions.
It also helps immensely to have a mechanism to replicate what you are experiencing.

Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Fri, Mar 28, 2014 at 8:41 AM, Lothar Kimmeringer <job@xxxxxxxxxxxxxx> wrote:
Am 28.03.2014 14:17, schrieb Joakim Erdfelt:
> What is hping2?

> That's a non-existant application on OSX, Linux, and Windows.

About 74.300 results (0,11 Seconds)

Interesting definition of non-existant ;-)

Regards, Lothar
jetty-users mailing list

Back to the top