Just found this on speedtest.net

Wondering what door on web-hell that line will open.

Ain't nothing truer.

the one of this values is created by the backend, so instead of add a variable and make it true or false you simply write it when you generate the response. Probably he checks against "true" and not just if (var), because it's js and something could go wrong.
I have use this approach some times, it's not the best, but it's a nice hack.

Holy shit. Even in the tragic desolate land of Javascript, this can't ever be a good idea.

@superuser if he can manipulate the response , he can either omit the if statement entirely when he wants it to be true , or delete the life if it's false. a better IMHO.

It's JavaScript though so I bet there's a way for 'true' not to be (strictly) equal to 'true'...

a the beta version of speed test.
it's a html based speed test instead of flash. it's really fast and more accurate I recommend it

@inpothet It redirects me to the beta version now since Chrome disables Flash by default (at least in the dev release). The filtering proxy at work currently blocks the servers used by the beta version though :/

I'll bet one of those "true" values is getting set with PHP or something.

the real reason why my speedtest results are bad..