WCCP service groups, numbers, IDs, and well-known services
A FortiProxy unit configured as a WCCP client can include multiple client configurations. Each of these configurations is called a WCCP service group. A service group consists of one or more FortiProxy units configured as WCCP servers (or routers) and one or more FortiProxy WCCP clients working together to cache a specific type of traffic. The service group configuration includes information about the type of traffic to be cached, the addresses of the WCCP clients and servers, and other information about the service.
A service group is identified with a numeric WCCP service ID (or service number) in the range 0 to 255. All of the servers and clients in the same WCCP service group must have service group configurations with the same WCCP service ID.
The value of the service ID provides some information about the type of traffic to be cached by the service group. Service IDs in the range 0 to 50 are reserved for well-known services. A well-known service is any service that is defined by the WCCP standard as being well known. Because the service is well known, you just need to specify the service ID to identify the traffic to be cached.
Even though the well-known service ID range is 0 to 50, only one well known service has been defined. Its service ID is 0, which is used for caching HTTP (web) traffic.
To configure WCCP to cache HTTP sessions, you can add a service group to the FortiProxy WCCP router and FortiProxy WCCP clients with a service ID of 0. No other information about the type of traffic to cache needs to be added to the service group.
Because service IDs 1 to 50 are reserved for well-known services and because these services are not defined yet, you should not add service groups with IDs in the range 1 to 50.
FortiProxy allows you to add service groups with IDs between 1 and 50. However, because these service groups have not been assigned as well-known services, they will not cache any sessions. Service groups with IDs 51 to 255 allow you to set the port numbers and protocol number of the traffic to be cached. So you can use service groups with IDs 51 to 255 to cache different kinds of traffic based on port numbers and protocol number of the traffic. Service groups 1 to 50 however, do not allow you to set port or protocol numbers, so they cannot be used to cache any traffic. |
To cache traffic other than HTTP traffic you must add service groups with IDs in the range 51 to 255. These service group configurations must include the port numbers and protocol number of the traffic to be cached. It is the port and protocol number configuration in the service group that determines what traffic will be cached by WCCP.