In message <_A3144@delegate-en.ML_>
you "Raphael Turbatte" <firstname.lastname@example.org> wrote:
|Trouble is, I can't figure out how Delegate handles the HTTP 307 reply that
|is issued by the transparent outbound proxy prior to authentication: my TCP
DeleGate does nothing for 307 response message. Since DeleGate does not
understand 307 code, it records the message header as "Error" in the
LOGFILE. It relays the response message as is from the server to the
client, without caching, closing the TCP connection.
|listener indicates Delegate sends an RST-flagged TCP packet resetting the
|connection, and the log indicates it tries to connect to
|https://mydomain.com (instead of http://mydomain which was the initial
|query). But it does not go to the (virtual) URL in the 307 response header.
|I tried to unset the MYAUTH parameter incase it implied trying to connect
|through SSL, but that didn't make any difference: Delegate still does not
|connect to the 307 redirection URL.
If your DeleGate tries to connect to https://..., then it is because
your client requested to do so, possibly by automatic redirection
indicated from the server-side. Inspecting the LOGFILE of DeleGate,
recorded during the series of requests and responses, will show us
what is happening.
D G Yutaka Sato <email@example.com> 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