03-24-2009 11:42 AM
Solved! Go to Solution.
03-24-2009 12:13 PM
03-24-2009 12:17 PM
This is problem i m trying to shout but nobody listning from symantec.
Norton new version i.e. 16.5 version doesn't support proxy connections.
LU servers are different and do not have HTTP/1.1 support.
I can't live update too.
Is symantec deaf or what, 4 days till i reported matter nothing is happenening no updates on the matter watsoever.
I tries tech suppor, forum, email and pms nothing works.
Nobdy replies. What a great support they give.
03-24-2009 12:48 PM
Norton new version i.e. 16.5 version doesn't support proxy connections. LU servers are different and do not have HTTP/1.1 support.
Ah, now that is information I did not have, and potentially useful. We need to update the proxy, so if the problem is that HTTP/1.1 isn't good enough for LiveUpdate, maybe an upgrade... What's the latest version of HTTP these days? [checks]
Wait, *is* there a newer version of HTTP than 1.1? Surely there must be, since 1.1 is certifiably older than dirt, but I can't find any reference to one.
Another thought: port 443 is unproxied here. Is there a way I can force LiveUpdate to use https?
03-24-2009 01:01 PM
I think there is a mistake by the previous poster, I think he mean to say LU no longer supports 1.0 not 1.1
Here is the Symantec response
The LiveUpdate engine was updated with the release of NAV/NIS 16.5 and Norton 360 v3. The new version of LiveUpdate engine will check if it receives HTTP 1.1 server responses, and explicitly reject HTTP 1.0 server responses. This was done to ensure that you are receiving updates from a valid LiveUpdate server. If you are using a proxy server, it could be configured to return HTTP 1.0 responses, and thus LiveUpdate will see this as an improperly configured connection.
A workaround for this issue is to disable the proxy server, or to reconfigure it. Most proxy servers can be configured to return HTTP 1.0 or 1.1 responses. We understand that this may not be possible for some users that are experiencing this issue. We are still working on a good solution for this issue. Thanks for your patience. "
However, be advised that I also consider there is a firewall issue, and it anyone is able to temporarily disable hardware firewalls in router/modems this may resolve the issue. Take a look at the log.lue and search for ERR lines and advise what you see.
03-24-2009 01:15 PM
In case it wasn't clear, in the other thread, one of the possible workarounds is to disable or to reconfigure your proxy server to return HTTP 1.1 responses. Can you try this and then see if you are still having the problem?
03-24-2009 01:15 PM
I think he mean to say LU no longer supports 1.0 not 1.1
However, be advised that I also consider there is a firewall issue, and it anyone is able to temporarily disable hardware firewalls in router/modems this may resolve the issue.
03-24-2009 01:25 PM
03-24-2009 03:04 PM
Ok glad yours appears to be a proxy issue with HTTP. Yes I appreciate not everybody can disable firewall. In any event it works for some users because it is confirmed in another thread. However, clearly there are more than one issue going on here. Since I am unsure of what a hardware firewall is doing viz vi http I cant say if the two are related in any way...yet!
03-26-2009 09:10 AM
Would you believe Squid doesn't fully support HTTP 1.1?
Color me flabbergasted. I was surely not aware that any software in widespread use, let alone something as major as Squid, still does not support a version of HTTP that came out during the first browser war.
But it's true. Apparently Squid supports retrieving content from servers via HTTP 1.1, but its server aspect doesn't quite support all of the client request features of 1.1, and so that's why it tells the client it's using HTTP 1.0. For the curious here's a link to a recent mailing list thread related to this issue.
So I ask again: is there a way to tell LiveUpdate to forget about port 80 and just use 443 for updates? I cannot imagine HTTP 1.1 would provide any relevant security that HTTPS wouldn't provide even better.