The block page sent to the client counts towards the traffic.
byte_to_client still has a value populated with the number of bytes the actual block page sends back.
Your block pages are about 3.5k each.
Thanks, Can I block the traffic before it is sent? If not can I remove this traffic from the summary page of the reporter?
What is the goal? To completely remove references to blocks from the reports, or to reduce the bytes for blocks to 0? Is it for all blocks, or just certain sites?
Man you are fast. Thanks very much for the help.
I was thinking that removing the traffic of blocked sites from the network all together would help thru-put. It seems unproductive to send those bytes to the client just to have them blocked.
I think that I can create a report that will only show 'allowed' so that should not be an issue.
Well, I don't think you want to completely get rid of the block pages since that is what tells the end user why their page isn't loading. If Web Gateway deosn't send a block page, then the user wouldn't know what's happening and could look like the server is down, or not responding.
If you know certain URLs are requests comeing from an application, such as streaming media site, or a stock ticker, then you could prevent a block page sent for them. But I really think you're talking about a very very small ammount of the total traffic and not likely to have any significant impact on your network thru-put. It doesn't seem worth the effort to investigate, implement, then manage. It's very likely that the ammount of work that Web Gateway would do to handle these special cases would be more load on the appliance.
Are you seeing performance issues for your web traffic? I'm wonding if we are still working back to what your real issue is.