From: Jan Humme <jan.humme@xs4all.nl>
To: Nathan Cassano <nathan@cjhunter.com>,
'Antony Stone' <Antony@Soft-Solutions.co.uk>,
netfilter@lists.samba.org
Subject: Re: HTTP Port forwarding issues
Date: Tue, 9 Jul 2002 11:52:39 +0200 [thread overview]
Message-ID: <02070911523900.05759@Lms> (raw)
In-Reply-To: <40fb01c226c7$5014e810$2901a8c0@amos>
Of course, HTTP runs over TCP, but who can explain why in /etc/services:
# grep http /etc/services
# http://www.isi.edu/in-notes/iana/assignments/port-numbers
http 80/tcp www www-http # WorldWideWeb HTTP
http 80/udp www www-http # HyperText Transfer Protocol
https 443/tcp # MCom
https 443/udp # MCom
gss-http 488/tcp
gss-http 488/udp
http-alt 8008/tcp
http-alt 8008/udp
Ports and port numbers are different for TCP and UDP, right?
Jan Humme.
On Monday 08 July 2002 23:35, Nathan Cassano wrote:
> Hmm... After a little research it appears that I am wrong. Darn, I hate
> looking like a fool. Sorry for the misinformation.
>
> RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
> ftp://ftp.isi.edu/in-notes/rfc2616.txt
>
> Antony Stone wrote:
> >> Remember HTTP runs over UDP protocol also.
> >
> >WHAT ?????
> >
> >RFC # ?
> >
> >
> >
> >Antony.
next prev parent reply other threads:[~2002-07-09 9:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 19:37 HTTP Port forwarding issues Big Daddy
2002-07-08 19:44 ` Tom Eastep
2002-07-08 19:51 ` Big Daddy
2002-07-08 19:56 ` Tom Eastep
2002-07-08 19:57 ` Antony Stone
2002-07-08 20:03 ` Big Daddy
2002-07-08 20:07 ` Antony Stone
2002-07-08 20:11 ` Stewart Thompson
2002-07-08 20:39 ` Big Daddy
2002-07-08 20:42 ` Antony Stone
2002-07-08 19:49 ` Antony Stone
2002-07-08 19:50 ` Stewart Thompson
2002-07-08 20:00 ` Darrell Dieringer
2002-07-08 20:25 ` Nathan Cassano
2002-07-08 20:50 ` Antony Stone
2002-07-08 21:20 ` Adam D. Barratt
2002-07-08 21:35 ` Nathan Cassano
2002-07-09 9:52 ` Jan Humme [this message]
2002-07-09 14:15 ` tcp/udp ports (was: Re: HTTP Port forwarding issues) James Sneeringer
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=02070911523900.05759@Lms \
--to=jan.humme@xs4all.nl \
--cc=Antony@Soft-Solutions.co.uk \
--cc=nathan@cjhunter.com \
--cc=netfilter@lists.samba.org \
/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