RE: httpapi and proxy servers

[Scott Klement <klemscot@xxxxxxxxxxxx>]

Sender: Scott Klement <klemscot@xxxxxxxxxxxx>


> So the destination address is further 'up' in the TCP headers somewhere and
> not part of the HTTP data. (Which is why I thought it might be clear).

The IP address, of course, is cleartext -- that's required in order to
route the datagrams.  But the "data" portion of the datagram is encrypted.


> Hence I don't need to 'see' my 443 http stuff in the sniffer to determine
> what the proxy is doing, I can change it to port 80.
>
> Therefor the main problem I forsee will be to transmit on a different port
> to 443, as our test proxy requires a port connection something like 8080.

Whether or not it's encrypted depends upon the protocol, not the port
number.  If a URL starts with http: then it's not encrypted.  If it starts
with https: then it is.

The DEFAULT port for http is 80, and for https it's 443.  However, you can
run those protocols on any port that you like.

For example, if I do the following, it will use port 1234 with encryption:

    https://www.example.com:1234/path/to/somedocument.html

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------