WCCP - Cache engine - URL filter - how it all works?

Nov 23, 2006 1 Replies

Rate this thread:

brickwalls19 19 years ago

I'm just trying to understand how the many network devices look at a HTTP packet and process it to the destination.

The network consists of a router (Cisco) with WCCP enabled to send HTTP packets to a cache engine (Cisco 511) which sends HTTP information to the URL filtering server (Surfcontrol).

So I'm at my desktop and I want to go to an authorized site like google.com and an unauthorized site like penthouse.com. My desktop sends an IP packet with an HTTP request.

Could someone possibly simply explain how each device will process my HTTP request? You can also state in terms of the OSI layer if necessary. Thanks.

Vote

Xuewei Wang 19 years ago

I only know the WCCP.The desktop send a http request to the router,then the router redirect the request to the cache engine by WCCP protocol.If the cache engine have the date,it send the date to the desktop.If not,the cache engine will get the date then send it to the desktop.

Vote

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required