On Sat, 8 Nov 2014 22:01:25 +0100, Henri Beauchamp wrote:

> Wild guess: a firewall/web cache on your ISP's side, filtering HTTP
> requests based off the user agent 

Scratch that, because any request on http://my.Secondlife.com (i.e.
any request on port 80) gets automatically redirected to
https://my.Secondlife.com (SSL or TLS, port 443), so your ISP can't
do a deep packet inspection to filter on the user agent (which is
encrypted with the rest of the request in this case).

However, your ISP's web proxy/firewall could prefectly refuse SSLv3
(and older) negociations on port 443: such a measure could have been
put recently into place because of the POODLE vulnerability.
In this event, older viewers not using the latest TLS v1.0-enabled
llqtwebkit won't be able to pass through your ISP's filter.

To verify whether it's the case or not, either try via Firefox
after configuring the latter to refuse all TLS (v1.0, 1.1, 1.2)
connections and accept SSL v3 only (Firefox would then fail to
load a web profile), or use another TPV that got the newer llqtwebkit
(the current releases of the Cool VL Viewer have it), which would
then succeed.

Henri.
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

Reply via email to