RE: [squid-users] http_proxy_authorization header

From: Chris Perreault <Chris.Perreault@dont-contact.us>
Date: Tue, 29 Jun 2004 08:49:01 -0400

Background: setting up a reverse proxy with ldap authentication, with said
authentication being passed down to the origin server.

When using

cache_peer 10.1.1.1 parent 80 0 originserver no-query no-digest proxy-only
login=*:password
cache_peer 10.1.1.45 parent 80 0 originserver no-query no-digest proxy-only
login=*:password
# cache_peer_domain lines map internal-redirect lines (ie URLs emmited by
redirect_program)
# to specific cache_peer hosts
cache_peer_domain 10.1.1.1 intranet-internal-redirect
cache_peer_domain 10.1.1.45 extranet-internal-redirect

I can retrieve the username, on the origin webserver by unencoding the
base64 encoded username. This arrives within the http_proxy_authorization
header.

I was looking to change the name of this header, and figured that squid
named the header. In the below directory I typed this, hoping to find it,
and then just change the name of it and recompile:

linux:/usr/src/packages/SOURCES/squid-3.0-PRE3-20040608 # grep -R http_proxy
*

And got no results. Does anyone know where this header gets its name from?
The other option is to just go and change the webpages, that are currently
looking for a different header for the username.

Chris Perreault
Received on Tue Jun 29 2004 - 06:49:13 MDT

This archive was generated by hypermail pre-2.1.9 : Thu Jul 01 2004 - 12:00:03 MDT