2012/4/12 Mehdi Sarmadi :
> you'r right just fixed it.
>
> allowTrace="false" connectionTimeout="2" clientAuth="false" />
>
> anyway, I can't still find the "Connection: Keep-Alive" HTTP Response(from
> tomcat) header. I just don't know where to check, any clues? anything
> missing?
>
>
> On T
Assuming keep-alive being on by default in HTTP/1.1 how come, apache does
not work that way?
I mean even I force HTTP/1.1 in apache with Keep-Alive On, it sends back
"Connection: KeepAlive" in HTTP Response?
Moreover, turning keepalive feature on, makes Apache response about 8 to 10
times more than
I just misunderstood, so you'r saying it is HTTP 1.0 we will have the
keep-alive in HTTP?
I'll check that.
--
Mehdi Sarmadi
On Thu, Apr 12, 2012 at 5:36 PM, Mehdi Sarmadi wrote:
> you'r right just fixed it.
>
> allowTrace="false" connectionTimeout="2" clientAuth="false" />
>
> anyway, I ca
you'r right just fixed it.
anyway, I can't still find the "Connection: Keep-Alive" HTTP Response(from
tomcat) header. I just don't know where to check, any clues? anything
missing?
--
Mehdi Sarmadi
On Thu, Apr 12, 2012 at 5:28 PM, Konstantin Kolinko
wrote:
> 2012/4/12 Mehdi Sarmadi :
> >
> >
2012/4/12 Mehdi Sarmadi :
>
> I just setup a tomcat 7 on linux for test. I just used this connection
> property in server.xml
>
> here is out connector
> allowTrace="false" connectionTimeout="2" clientAuth="false" />
>
> , but when we try to connect from a client "Firefox" in my case,
> "Conn
Hi
I just setup a tomcat 7 on linux for test. I just used this connection
property in server.xml
here is out connector
, but when we try to connect from a client "Firefox" in my case,
"Connection: Keep-Alive" is sent in the Request by Browser but "Connection:
Keep-Alive" is not visible in the
