[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Summary of ICAP discussion

To: Martin Stecher <martin.stecher@xxxxxxxxxxxxx>
Subject: Re: Summary of ICAP discussion
From: Andre Beck <abeck@xxxxxxxxxxxxx>
Date: Fri, 18 Oct 2002 17:49:28 -0400
Cc: OPES Group <ietf-openproxy@xxxxxxx>
List-archive: <http://www.imc.org/ietf-openproxy/mail-archive/>
List-id: <ietf-openproxy.imc.org>
List-unsubscribe: <mailto:ietf-openproxy-request@imc.org?body=unsubscribe>
References: <>
Sender: owner-ietf-openproxy@xxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826


Martin Stecher wrote:
> re (4): Most implementations support the X-Client-IP header. I don't
> know any implementation supporting X-Subscriber-ID.

The Bell Labs ISE (ICAP server) as well as our ICAP client library support both headers. Applications incorporating our ICAP client library can set the X-Client-IP and X-Subscriber-ID headers when sending ICAP requests and service modules for the ISE have access to the values of these headers (if present).

-Andre

References:
- RE: Summary of ICAP discussion
  - From: Martin Stecher

Prev by Date: Re: Summary of ICAP discussion
Next by Date: AW: Summary of ICAP discussion
Previous by thread: Re: Summary of ICAP discussion
Next by thread: OPES Scenarios
Index(es):
- Date
- Thread