reports keepalive as off?

WebPageTest Private Instances
1

Hi,

I just installed the hosted version in a windows vm to test some local and international sites from my ISP…

but for my own site, it reports keep-alive to be off. the keep alove is recognised correctly for other hostnames.

the online version of webpagetest.org reports i have set keep-alive on…

What could be wrong? All IPs are served from the same server and the affected requests dont touch a CDN. only requests from www.thaindian.com show as not using keepalive

Might be worth mentioning that my ISP uses an aggresive transparent proxy ( HTTP/1.1 NetScaler ) to save international bandwidth.

Attached the raw object data.

Is there a definative guide somewhere to test for keepalive?

2

From the results file it looks like most of the requests that are failing are for cdn.wibiya.com (specifically in the /Graphics_Toolbar path).

Have you looked at the response (and request) headers for the internal tests vs. the ones run on the public instance? There’s a good chance that your ISP’s proxy is forcing the connection behavior (and possibly downgrading to HTTP 1.0) which would make it pretty useless to test from your ISP’s connection.

Thanks,

-Pat

3

Strange, when i run my homepage keepalive is working for my domain, but when i run a deeper url it doesnt

response headers in firebug :-

HTTP/1.1 200 OK Server: nginx/0.7.67 Date: Tue, 06 Jul 2010 18:00:18 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Content-Encoding: gzip

request/response headers in private hosted webpagetest :-

[code]URL: http://www.thaindian.com/newsportal/entertainment/anne-hathaway-to-star-in-a-new-cinderella-story_100381412.html
Host: www.thaindian.com
IP: 174.37.198.150
Error/Status Code: 200
Start Offset: 0 s
DNS Lookup: 62 ms
Initial Connection: 149 ms
Time to First Byte: 591 ms
Content Download: 254 ms
Bytes In (downloaded): 16.1 KB
Bytes Out (uploaded): 0.4 KB

Request Headers:

GET /newsportal/entertainment/anne-hathaway-to-star-in-a-new-cinderella-story_100381412.html HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, /
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; PTST 2.222)
Accept-Encoding: gzip, deflate
Host: www.thaindian.com
Connection: Keep-Alive

Response Headers:

HTTP/1.1 200 OK
Server: nginx/0.7.67
Date: Tue, 06 Jul 2010 18:06:37 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip
Age: 0[/code]

request/response headers in public hosted webpagetest at webpagetest.org :-

[code]Request 1:

URL: http://www.thaindian.com/newsportal/entertainment/anne-hathaway-to-star-in-a-new-cinderella-story_100381412.html
Host: www.thaindian.com
IP: 174.37.198.148
Location: Dallas, TX*
Error/Status Code: 200
Start Offset: 0 s
DNS Lookup: 202 ms
Initial Connection: 118 ms
Time to First Byte: 140 ms
Content Download: 290 ms
Bytes In (downloaded): 16.1 KB
Bytes Out (uploaded): 0.6 KB

Request Headers:

GET /newsportal/entertainment/anne-hathaway-to-star-in-a-new-cinderella-story_100381412.html HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-shockwave-flash, /
Accept-Language: en-us
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; PTST 2.219; PTST 2.219)
Host: www.thaindian.com
Connection: Keep-Alive

Response Headers:

HTTP/1.1 200 OK
Server: nginx/0.7.67
Date: Tue, 06 Jul 2010 18:09:59 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Content-Encoding: gzip[/code]

My main intention is to test how locally hosted pages open up within Thailand. Locally hosted pages bypass the evil transparent proxy…

wibiya toolbar has not given 1 cent of thought on performance… i am still using them cause i add their js only after everything is loaded.