[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: HTTPAPI: TCP Forwarder
Hello Scott,
yes, you are right. It is a device that simply forwards the TCP channel. Therefore I need to start the process by sending HTTP_URL_POST with the URL of the TCP forwarder and change the host-information (which is automatically set by the procedure) of the http-header to the correct host name of the final destination. As far as I could verify, this is not possible with the http_setproxy.
Mit freundlichen Grüßen/Best regards Mag. Alexander Grünwald
Geschäftsführer/Projektmanagement
SOB Datenverarbeitungsges.m.b.H.
Albrechtstraße 60/9
A-3400 Klosterneuburg
Tel. +43/2243/37201
Fax. +43/2243/37201/5
Mail: alexander.gruenwald@xxxxxxxxxxx
-----Ursprüngliche Nachricht-----
Von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] Im Auftrag von Scott Klement
Gesendet: Donnerstag, 16. Juli 2015 00:01
An: HTTPAPI and FTPAPI Projects
Betreff: Re: HTTPAPI: TCP Forwarder
Hello Alexander,
What do you mean by "TCP forwarder", exactly? If you mean that it
simply forwards TCP channel to a given host, then yes, the final destination will get the wrong hostname in the HTTP headers that way.
This should happen with all HTTP clients, as these forwarders do not understand the HTTP protocol and therefore will not change the header information for you automatically.
Using proxy (with http_setproxy) is the correct solution. However, this will not work with a device that simply forwards a TCP channel, it needs to be an HTTP proxy instead.
But, perhaps this is what you mean by "TCP forwarder"?
Please provide more information.
-SK
On 6/23/2015 7:19 AM, Alexander Grünwald wrote:
> Hello all !!
>
>
> I am using HTTPAPI for Webservices successfully for a long time. Now I
> am facing a problem with my communication using a TCP Forwarder Gateway
> for a new WebService request. Due to audit rules, I may not access an
> outside Webservice directly. Therefore I have got a TCP-Forwarder,
> which I have been using in the past for another client without any
> problems.
>
>
> Checking the logs, I can see, that the http_url_post uses the
> gateway-name and port to receive my request and hopefully forwards it
> without any changes (it is SSL encrypted). But the final destination
> seems to reject the SOAP request due to the fact, that the Host-part of
> my request doesn´t contain the final destination but my tcp-gateway.
>
>
> Is there anybody out there, who has had a similar problem and can give
> me advice ? I have been trying to use
> http_setproxy(`Gateway.com':10069) and
> http_url_post(`https://finaldestination.com': soapmessage, etc ...) to
> get it up and running, but I cannot access the WebService.
>
>
> Thanks for your help and best regards, Alexander
>
>
>
> ----------------------------------------------------------------------
> - This is the FTPAPI mailing list. To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------