[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: httpapi and proxy servers
Sender: "Ian Patterson" <ian@xxxxxxxxxxxxxxxxxxxx>
Thanks again Scott,
This increases my understanding of the httpapi. I did not know I could
change the port in the way you suggested.
It seems too simple.. :-)
Therefore when using a proxy (not yet got the password & logging in sorted
out), it is a simple matter to change ports :
<original code>
eval rc=http_url_get(https://remoteserver.com/submissions/loginApp.do:
etc..)
and eval
rc=http_url_post(https://remoteserver.com/submissions/authenticate.do:
etc..)
<new code>
eval rc=http_url_get(https://remoteserver.com:8080/submissions/loginApp.do:
etc..)
and eval
rc=http_url_post(https://remoteserver.com:8080/submissions/authenticate.do:
etc..)
where the proxy is operating on port 8080
We have now got our Windows application conversation to the proxy mapped ,
so can start to apply to the AS/400.
Regards
Ian Patterson
ian@xxxxxxxxxxxxxxxxx <mailto:ian@xxxxxxxxxxxxxxxxx>
Grange IT Limited
tel 01947 880458
www.grangesystems.com
-----Original Message-----
From: owner-ftpapi@xxxxxxxxxxxxx [mailto:owner-ftpapi@xxxxxxxxxxxxx]On
Behalf Of Scott Klement
Sent: 16 September 2004 00:09
To: ftpapi@xxxxxxxxxxxxx
Subject: RE: httpapi and proxy servers
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
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------