ons 2006-06-21 klockan 00:49 -0400 skrev Michael Carpenter:
> List,
>
> We have a group of SLES systems in a private, non-routable subnet that
> we provide Internet/intranet access to via a Squid proxy. This works
> great for proxying normal HTTP traffic through, but we are having
> problems getting non-anonymous FTP through the proxy. The YaST client
> does not allow you to specify an FTP username in the form
> ftp://user@hostname <ftp://user@hostname/>, but rather sends both a
> Proxy-authorization and an Authorization entity in the HTTP header.
Ouch...
> My question: Is there any way to instruct Squid to use these credentials
> for FTP login? I read somewhere that Squid is not permitted to forward
> authorizations in which it "consumes", but is there a way to prevent
> Squid from consuming these credentials? I would prefer to avoid using a
> transparent proxy if possible...do I have any other options?
You need to modify Squid to do this. See the ftpCheckAuth() function.
It's somewhat outside the standards to not send the login & password in
the URL, but not a bad idea as such..
Regards
Henrik
This archive was generated by hypermail pre-2.1.9 : Sat Jul 01 2006 - 12:00:02 MDT