| Author |
Message |
Henry
Guest
|
Posted:
Wed Feb 23, 2005 3:01 am Post subject:
Can't view video on client with Symantec Client Firewall ins |
|
|
Below is a snip from an email I got from Symantec support. In short they are
indicating my WMS is handing off compressed web pages as links to the
streaming content. This server does not run IIS. Requests for videos come
from a different server that forwards requests to my WMS. I get the web page
from the other server just fine, but the imbedded video never starts. Is
there a way to tell the WMS to not send comressed web pages?
Frankly I don't get what this guy is saying, but I want to be sure I know
what I'm talking about before I ask him for some of what he's smoke'en!
FROM SUPPORT EMAIL:
================================================
The information I have received is that what may be causing the issue with
your Streaming Video servers is that Symantec Client Firewall is stripping a
line from the code intentionally. The following is what occurs:
1. The following line comes through SCF:Accept-Encoding: gzip, deflate
2. SCF replaces this with: ---------------: ----- -------
3. This is due to the fact that SCF cannot scan compressed web pages and
therefore does not support this compression.
4. Taking out this line should tell the server to re-send the page without
the compression
|
|
| Back to top |
|
 |
Neil Smith [MVP Digital M
Guest
|
Posted:
Wed Feb 23, 2005 3:56 pm Post subject:
Re: Can't view video on client with Symantec Client Firewall |
|
|
Then there's a serious problem with the Symantec firewall which is
independent of WM Serve, it would affect any HTTP server which meets
the HTTP specification :
http://www.comptechdoc.org/independent/web/http/reference/httprequest.html
Compressed (gzipped) pages are also commonly used by web servers.
In fact, the client browser indicatesto the server whether it is
capable and wants to accept zipped pages (it's a header the client
sends, usually like "Accept-Encoding: compress, gzip")
If you do this (and I have regularly) you send about 30-50% of the
actual page weight down the wire because it's compressed (zipped),
which in general makes the page load faster and the server bandwidth
lower. So it's a desirable technique.
Symantec need to fix their code to unzip pages and not be such nancys.
Cheers - Neil
On Tue, 22 Feb 2005 14:01:07 -0800, "Henry"
<Henry@discussions.microsoft.com> wrote:
| Quote: | Below is a snip from an email I got from Symantec support. In short they are
indicating my WMS is handing off compressed web pages as links to the
streaming content. This server does not run IIS. Requests for videos come
from a different server that forwards requests to my WMS. I get the web page
from the other server just fine, but the imbedded video never starts. Is
there a way to tell the WMS to not send comressed web pages?
Frankly I don't get what this guy is saying, but I want to be sure I know
what I'm talking about before I ask him for some of what he's smoke'en!
FROM SUPPORT EMAIL:
================================================
The information I have received is that what may be causing the issue with
your Streaming Video servers is that Symantec Client Firewall is stripping a
line from the code intentionally. The following is what occurs:
1. The following line comes through SCF:Accept-Encoding: gzip, deflate
2. SCF replaces this with: ---------------: ----- -------
3. This is due to the fact that SCF cannot scan compressed web pages and
therefore does not support this compression.
4. Taking out this line should tell the server to re-send the page without
the compression
|
|
|
| Back to top |
|
 |
Henry
Guest
|
Posted:
Wed Feb 23, 2005 7:49 pm Post subject:
Re: Can't view video on client with Symantec Client Firewall |
|
|
I agree with your sentiment, but if I’m going to prove or disprove the
assessment made by Symantec support, I have to disable the compression. If I
can not do this on the server, do you know how configure IE to indicate it
can’t handle compression?
"Neil Smith [MVP Digital Media]" wrote:
| Quote: | Then there's a serious problem with the Symantec firewall which is
independent of WM Serve, it would affect any HTTP server which meets
the HTTP specification :
http://www.comptechdoc.org/independent/web/http/reference/httprequest.html
Compressed (gzipped) pages are also commonly used by web servers.
In fact, the client browser indicatesto the server whether it is
capable and wants to accept zipped pages (it's a header the client
sends, usually like "Accept-Encoding: compress, gzip")
If you do this (and I have regularly) you send about 30-50% of the
actual page weight down the wire because it's compressed (zipped),
which in general makes the page load faster and the server bandwidth
lower. So it's a desirable technique.
Symantec need to fix their code to unzip pages and not be such nancys.
Cheers - Neil
On Tue, 22 Feb 2005 14:01:07 -0800, "Henry"
Henry@discussions.microsoft.com> wrote:
Below is a snip from an email I got from Symantec support. In short they are
indicating my WMS is handing off compressed web pages as links to the
streaming content. This server does not run IIS. Requests for videos come
from a different server that forwards requests to my WMS. I get the web page
from the other server just fine, but the imbedded video never starts. Is
there a way to tell the WMS to not send comressed web pages?
Frankly I don't get what this guy is saying, but I want to be sure I know
what I'm talking about before I ask him for some of what he's smoke'en!
FROM SUPPORT EMAIL:
================================================
The information I have received is that what may be causing the issue with
your Streaming Video servers is that Symantec Client Firewall is stripping a
line from the code intentionally. The following is what occurs:
1. The following line comes through SCF:Accept-Encoding: gzip, deflate
2. SCF replaces this with: ---------------: ----- -------
3. This is due to the fact that SCF cannot scan compressed web pages and
therefore does not support this compression.
4. Taking out this line should tell the server to re-send the page without
the compression
|
|
|
| Back to top |
|
 |
|
|
|
|