From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Proxy support for zftp functions
Date: Mon, 22 May 2000 16:33:55 +0100 [thread overview]
Message-ID: <0FUY009L8WKJGE@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Mon, 22 May 2000 19:01:57 +0400." <000901bfc3fe$acab7310$21c9ca95@mow.siemens.ru>
> I'd like to add proxy support to these. Looking around, it looks, like
> it enough to add a couple of lines to zfopen - but I'm not sure, if
> there can be any side effects (e.g. we set ZFTP_HOST but open real
> connection to another host).
This was on my original plan, but not only didn't I need it myself I didn't
even have a proxy host to try on, so I never thought much about it.
I was actually imagining doing it in the C code. But if the server is
configured suitably, you ought to get away with it. The parameters
ZFTP_HOST, ZFTP_USER etc. are readonly, but not special, and are not
checked by the C code, only set by it, so running typeset +r then changing
the variable after the connection is open and a user logged in should be
OK. I don't actually know how proxies work, having never used one, but if
logging into a remote server involves sending a special username to the
proxy server there shouldn't be a problem.
--
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2000-05-22 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-22 15:01 Andrej Borsenkow
2000-05-22 15:33 ` Peter Stephenson [this message]
2000-05-22 16:03 ` Andrej Borsenkow
2000-05-22 16:17 ` Peter Stephenson
2000-05-22 16:35 ` Andrej Borsenkow
2000-05-22 17:04 ` Peter Stephenson
2000-05-23 0:19 ` Bart Schaefer
2000-05-23 0:43 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0FUY009L8WKJGE@la-la.cambridgesiliconradio.com \
--to=pws@cambridgesiliconradio.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).