On 07/09/05(05:24) you "Mike Vidal" wrote
|> But note that even when data is cached and served by the DeleGate,
|DeleGate makes a control connection to the origin server of the data.
|Is this for authentication purposes only?
No. It is because caching-proxy-FTP-DeleGate does not support the
full-set of commands and status of the FTP protocol, so it forwards
unknown or not cared commands to the origin server.
For example, DeleGate does not create a control connection to the
server if a file in it "ftp://server/dir/file" is cached and retrieved
with a stateless command like this:
But it makes a control connection to server if the command is a
sequence of CWD and RETR like this.
I think it is not difficult to modify FTP-DeleGate not to forward CWD
to the server (on a created control connection on demand) if the directry
is cached, but it might not be so easy to make any (statefull) commands
and responses be cared and cached consistently.
D G Yutaka Sato 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