[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Patch to add direct FTP proxy support in kio_ftp
From:       Michael Goffioul <goffioul () imec ! be>
Date:       2001-06-28 18:21:23
[Download RAW message or body]

> OK, I looked at the recent code (revision 1.95 of kprotocolmanager.cpp), and it still
> won't work in my case, because the FTP proxy is not part of the auto-proxy script.
> This script will return either DIRECT or a HTTP proxy, never the FTP proxy. That's
> why I have to override the auto-proxy settings and to add the test before the switch
> statement.
> But I guess then it is more a local configuration problem, and the script should
> be changed (unfortunately, I don't have acces to it, or maybe I should use a local
> copy of it, hacked).

I tried to hack my auto-proxy script such that it returns "PROXY ftp://ftpproxy:8028"
if the url starts with "ftp://", but again it won't work. In kpac_impl.cc, you'll
see that if the url returned by the script doesn't start with "http://", then it
will be prepended automatically, which results in
"http://ftp://ftpproxy:8028", giving again http as protocol (and an error). I really
wonder if an auto-proxy script may return something else than an HTTP proxy, and if
it wouldn't be best to separate an auto-proxy from real FTP proxy, as I did.
Otherwise you have to also make changes to kpac code. What is the standard on that
topic. May the JS script returns something else than an HTTP proxy?

Bye.
Michael.

-- 
------------------------------------------------------------------
Michael Goffioul		IMEC-DESICS-MIRA
e-mail: goffioul@imec.be	(Mixed-Signal and RF Applications)
Tel:    +32/16/28-8510		Kapeldreef, 75
Fax:    +32/16/28-1515		3001 HEVERLEE, BELGIUM
------------------------------------------------------------------
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]