[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <200311190506.hAJ56owS008919@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Sidewinder G2
On Tue, 18 Nov 2003 14:49:14 MST, you said:
> So if you have a HTTP application level proxy does that mean you are
> running a webserver ?
Please read RFC821 and/or 2821. 'SMTP Server' basically refers to *anything*
that's the server end of an SMTP conversation (RFC2821, section 2.1):
An SMTP server may be either the ultimate destination or an
intermediate "relay" (that is, it may assume the role of an SMTP
client after receiving the message) or "gateway" (that is, it may
transport the message further using some protocol other than SMTP).
SMTP commands are generated by the SMTP client and sent to the SMTP
server. SMTP replies are sent from the SMTP server to the SMTP
client in response to the commands.
Also, RFC2616 says this about HTTP proxies in section 1.3:
proxy
An intermediary program which acts as both a server and a client
for the purpose of making requests on behalf of other clients.
Requests are serviced internally or by passing them on, with
possible translation, to other servers. A proxy MUST implement
both the client and server requirements of this specification. A
So yes, if you're running a proxy, it *MUST* function as a server.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20031119/d85fdab9/attachment.bin
Powered by blists - more mailing lists