From: Alex Rousskov Date: Tue, 6 Sep 2011 20:10:26 +0000 (-0600) Subject: Adjusted cf.data.pre to reflect cross-vectoring point adaptation plan support. X-Git-Tag: take08~24^2~1 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=24b143e62502bf72c60ad94e16674e31f52dfb8c;p=thirdparty%2Fsquid.git Adjusted cf.data.pre to reflect cross-vectoring point adaptation plan support. These documentation changes were somehow missed from the r11327 commit that introduced support for dynamic adaptation plans that cover multiple vectoring points. --- diff --git a/src/cf.data.pre b/src/cf.data.pre index 6737e056eb..0017664fa5 100644 --- a/src/cf.data.pre +++ b/src/cf.data.pre @@ -6574,11 +6574,12 @@ DOC_START returning a chain of services to be used next. The services are specified using the X-Next-Services ICAP response header value, formatted as a comma-separated list of service names. - Each named service should be configured in squid.conf and - should have the same method and vectoring point as the current - ICAP transaction. Services violating these rules are ignored. - An empty X-Next-Services value results in an empty plan which - ends the current adaptation. + Each named service should be configured in squid.conf. Other + services are ignored. An empty X-Next-Services value results + in an empty plan which ends the current adaptation. + + Dynamic adaptation plan may cross or cover multiple supported + vectoring points in their natural processing order. Routing is not allowed by default: the ICAP X-Next-Services response header is ignored.