View Single Post
  #3  
Old 11th July 2012, 00:08
Ovidiu Ovidiu is offline
Senior Member
 
Join Date: Sep 2005
Posts: 1,258
Thanks: 76
Thanked 23 Times in 19 Posts
Default

That is really weird, I just tried again and you are right. I haven't changed anything since posting here.

Ok, well, lets leave it at that but does this look like its bad or can I just ignore it? Rings any bells with you?


Quote:
[Tue Jul 10 11:24:48 2012] [warn] [client 196.215.78.72] [stream 23] [6228:7199:WARNING:http_to_spdy_filter.cc(113)] HttpToSpdyFilter is not the last filter in the chain: http_to_spdy
[Tue Jul 10 14:19:40 2012] [error] [client 41.4.86.229] [21050:21050:ERROR:mod_spdy.cc(470)] Speculative read failed with status 104: Connection reset by peer
[Tue Jul 10 16:29:05 2012] [error] [client 93.186.22.251] [22055:22055:ERROR:mod_spdy.cc(470)] Speculative read failed with status 20014: Internal error
[Tue Jul 10 17:08:04 2012] [warn] [client 85.176.138.196] [stream 95] [32656:310:WARNING:spdy_to_http_filter.cc(168)] Unsupported read mode (2) on stream 95
Can I also add a slightly related question:

If I have a site where I only need HTTPS for maybe 3 URLs (i.e. a shopping cart, checkout, etc.) is it best to keep only those pages secured or rather go with the whole site for HTTPS?
Speed-wise is a non-https page or a https-page with mod_spdy and the proper browser faster for the end user?
Reply With Quote