[Reference:<_A3613@delegate-en.ML_>]
Newsgroups: mail-lists.delegate-en
[DeleGate-En] Re: How to bypass an upstream proxy server?
Hi,
In message <_A3613@delegate-en.ML_> on 01/24/07(20:36:41) I wrote:
| |$DELEGATED_BIN \
| | ADMIN="$MAIL" \
| | SERVER=http \
| | MYAUTH="user:password" \
| | $PORT \
| | MOUNT="/* https://www.grundbuch-sh.de/egbaks/*" \
| | DGROOT="$DIR" \
| | PERMIT="$PERMIT" \
| | SSLTUNNEL="$SSLTUNNEL" \
| | HTTPCONF="ver:1.1"
| |
| |Where:
| |
| |SSLTUNNEL="hostname.remoteproxy.datacenter.de:xxxx"
| |PORT="-P8083"
| |PERMIT="*:193.101.67.139:*.our.domain.name/@"
|
|You need to specify inserting a SSL filter into the connection with ther
|server as this:
|
| STLS=fsv
You can peep the HTTP request message sent to the HTTPS/SSL server adding
a parameter as follows:
FTOSV=-tee-n
Testing with the parameter, I found that the authentication information
by MYAUTH for SSLTUNNEL is also forwarded to the origin HTTPS/SSL server
in the Authorization header. It can be erased with the following parameter.
HTTPCONF=del-qhead:Authorization
I fixed DeleGate not to do such forwarding by default in DeleGate/9.4.3-pre3
released today.
Cheers,
Yutaka
--
9 9 Yutaka Sato <y.sato@delegate.org> http://delegate.org/y.sato/
( ~ ) National Institute of Advanced Industrial Science and Technology
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller
|