[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Try consume Soap Message from DHL need to use port 8300
Hello Scott,
Many thanks.
Will do and let you know.
Not sure if you have also seen my last email.
In that case I added :pePort:8300 as fixed text at the end of the URL.
Then I got at least the certificates exchanged.
Get back to you.
Kind Regards,
Arco van der Dussen
IT department
Hitachi Transport System
Achterweg 29, 4181 AD Waardenburg
PO BOX 167, 4190 CD Geldermalsen, The Netherlands
( +31 (0) 418 657 676
F +31 (0) 418 657 667
* arco.vanderdussen@xxxxxxxxxxxxxxxxxxxxxxx
ü www.hitachitransport-eu.com
P Please consider the Environment before printing this email.
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: 22 August 2012 16:12
To: HTTPAPI and FTPAPI Projects
Subject: Re: Try consume Soap Message from DHL need to use port 8300
Hello Arco,
I'm thinking this might be a bug in the way HTTPAPI performs SSL through a proxy. I suspect this manifests itself only when a port number is given to the proxy_tunnel subprocedure in HTTPAPIR4. The code looks like this:
c if pePort=0
c if peServ='https'
c eval wwPort=443
c else
c eval wwPort=80
c endif
c endif
c eval wwReq = 'CONNECT ' + %trim(peHost)
c + ':' + %trim(%editc(wwPort:'L'))
c + ' HTTP/1.1'
C + CRLF
So if a zero is passed for the port number (pePort is the parameter) then wwPort (the port number it actually uses) will be set to 80 or 443, the default HTTP/HTTPS port numbers. That makes perfect sense. But, what does it set wwPort to when 8300 is passed for the port numbre? As far as I can tell... it leaves it un-set, which isn't what it should do.
This is corroborated by the following line in your debug/trace file:
CONNECT www.wsbuat.dhl.com:0 HTTP/1.1
So... wwPort has been set to 0. It's telling the proxy to make a connection to the server on port 0 instead of 8300. Not good at all.
Can you try something for me? Can you try adding a line of code before
this IF statement:
c if pePort=0
c if peServ='https'
c eval wwPort=443
c else
c eval wwPort=80
c endif
c endif
The line of code would simply be:
c eval wwPort = pePort
After the changes the code should look like this:
c eval wwPort = pePort
c if pePort=0
c if peServ='https'
c eval wwPort=443
c else
c eval wwPort=80
c endif
c endif
If you make those changes and recompile HTTPAPI (just CALL INSTALL to do
that) does it solve your problem? (Or, at least improve the situation?)
Please let me know, because if it does, I'll need to make that change in the base code as well, and issue a new release.
-SK
On 8/21/2012 7:33 AM, van der Dussen, Arco wrote:
> Hello all,
>
>
>
> Sorry to say, I am new to webservices.
>
> I am very grateful for the httpapi sources and the examples included.
>
> This is a very good starting point together with the powerpoints on
> this topic.
>
> Compliments for that!
>
>
>
> After trying some examples that were included, I succeeded to get two
> Soap projects working.
>
> Consuming web services of UPS and one of TNT.
>
>
>
> Now I am stuck with my third webservice to DHL.
>
> The endpoint in SoapUI is stated as:
> [1]https://wsbuat.dhl.com:8300/gbl/expressRateBook
>
> also tried [2]https://www.wsbuat.dhl.com:8300/gbl/expressRateBook
>
>
>
> See the attached httpapi_debug.txt . I guess this part states my
> problem :0 versus :8300
>
> CONNECT [3]www.wsbuat.dhl.com:0 HTTP/1.1
> Host: [4]www.wsbuat.dhl.com:8300 HTTP/1.1
>
>
>
> I get an Internal server error when I use the URL with port number 8300
> included (as received from the SoapUI project by DHL)
>
>
>
> In the webservices I would see in httpapi_debug.txt CONNECT 443. The
> port number was not included in the "URL/Site".
>
>
>
> I have found the "callp http_long_ParseURL" which can retrieve the
> port Number for me from the URL.
>
> But how can I 'set' this port to be used in the http_url_post_xml?
>
>
>
> If I leave the port number 8300 out of the URL then I get a different
> error message ([5]https://wsbuat.dhl.com/gbl/expressRateBook)
>
> SSL Handshake: (GSKit) Peer not recognized or badly formatted
> message
>
>
>
> Hope someone can help me out.
>
>
>
> Much appreciated.
>
>
>
> Kind Regards,
>
>
> Arco van der Dussen
>
>
>
> ***********************************************************************
> ***************************
> E-mail Confidentiality Notice and Disclaimer.
>
> This e-mail and any files transmitted with it are confidential and are
> intended solely for the use of the individual or entity to which they
> are addressed. Access to this e-mail by anyone else is unauthorised. If
> you are not the intended recipient, any disclosure, copying,
> distribution or any action taken or omitted to be taken in reliance on
> it, is prohibited.
> E-mail messages are not necessarily secure.
> Hitachi does not accept responsibility for any changes made to this
> message after it was sent.
> Hitachi checks outgoing e-mail messages for the presence of computer
> viruses.
> ***********************************************************************
> ***************************
>
> References
>
> 1. https://wsbuat.dhl.com:8300/gbl/expressRateBook
> 2. https://www.wsbuat.dhl.com:8300/gbl/expressRateBook
> 3. http://www.wsbuat.dhl.com:0/
> 4. http://www.wsbuat.dhl.com:8300/
> 5. https://wsbuat.dhl.com/gbl/expressRateBook
>
>
>
> ----------------------------------------------------------------------
> - This is the FTPAPI mailing list. To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
**************************************************************************************************
E-mail Confidentiality Notice and Disclaimer.
This e-mail and any files transmitted with it are confidential and are intended solely for the use
of the individual or entity to which they are addressed. Access to this e-mail by anyone else is
unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited. E-mail messages are not
necessarily secure. Hitachi does not accept responsibility for any changes made to this message
after it was sent.
Hitachi checks outgoing e-mail messages for the presence of computer viruses.
**************************************************************************************************
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------