From: "Skip Tavakkolian" <fst@centurytel.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] circular logic (was webdav...)
Date: Mon, 4 Nov 2002 15:32:45 -0500 [thread overview]
Message-ID: <b6c2df665ee01e742c1296e8fe0c5efe@centurytel.net> (raw)
It is a circuitous approach -- forced by many external factors -- that
gets to the right solution (eventually). Something like: the
proxy/firewall device doesn't know the protocol, therefore the IT
department wont allow it, which forces the HTTP tunneling, which gives
the system/protocol a chance to become popular, which makes it a
legitimate protocol and gets it on the vendors' radars, which is then
supported, obviating the need for tunneling.
> non-http protocols are dangerous.
> therefore we'll only allow http.
>
> only http is allowed.
> therefore we'll tunnel everything over http.
next reply other threads:[~2002-11-04 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 20:32 Skip Tavakkolian [this message]
2002-11-04 22:27 Russ Cox
2002-11-05 1:43 ` Jonathan Sergent
2002-11-05 2:51 presotto
2002-11-05 3:34 Russ Cox
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=b6c2df665ee01e742c1296e8fe0c5efe@centurytel.net \
--to=fst@centurytel.net \
--cc=9fans@cse.psu.edu \
/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.
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).