[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: ContractFilter mismatch
I was just looking into why I needed the ConnClose proc. Being a newbie on
httpapi, I copied another program as my starting point. I removed the
ConnClose proc and it works now.
I also went back in and removed the <!xxx> comment lines and set my content
type same as the WSDL.
Thanks for all your help.
Ken
-----Original Message-----
From: Scott Klement [mailto:sk@xxxxxxxxxxxxxxxx]
Sent: Thursday, February 16, 2012 11:35 AM
To: HTTPAPI and FTPAPI Projects
Subject: Re: ContractFilter mismatch
Hi Ken,
I agree with Mike about the problem...
An "exit proc" (http_xproc) is called *during* the HTTP transaction, it's
not called when you declare it. If you set the ADDL_HEADER point twice, the
second one replaces the first one... so your SoapAction is never added.
I don't understand why you are specifying 'Connection: close'. Were you
having problems with it the normal way? There was a compatibility issue in
HTTPAPI many, many years ago where this was necessary, but surely it's not
needed now? (You're running version 1.23)
Also, if you update to version 1.24 (the current version) you don't need the
goofy ADD_SOAPACTION workaround, since 1.24 allows you to specify longer
soapaction values directly on the call to http_url_post_xml.
So, Ken, if I were you, I'd update to 1.24 and eliminate both xprocs.
If you /don't/ want to update, then I'd just eliminate the 'ConnClose',
because I don't think that's doing you any good.
If you need the ConnClose (for a reason I don't currently understand) then
you should combine the soapaction and connclose into a single xproc. But
I'd only do that as a last resort. One kludge is bad enough, but two is
overwhelming.
On 2/16/2012 10:46 AM, Mike Krebs wrote:
> Pretty easy to figure out now...should have seen this before. You are not
sending the SOAPAction.
>
> This isn't how this works...
>
> http_xproc(HTTP_POINT_ADDL_HEADER : %paddr(Add_SOAPACTION));
>
> http_xproc(HTTP_POINT_ADDL_HEADER : %paddr(ConnClose));
>
> What this does is set the addl_header exit point to first Add_SOAPACTION
and then sets it to ConnClose. So only ConnClose is getting called (last one
wins). It isn't ACTUALLY setting the additional header. It is setting the
procedure to be called when you make the request.
>
> So, combine them into one procedure and it will work.
>
> Also, set the content type to be same as the WSDL.
>
> In production (and even now), I think all the<!--optional--> should be
removable. Someone can correct me if I am wrong, but no need to junk up the
requests with the extra garbage.
>
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Ken
> Kantorowicz
> Sent: Thursday, February 16, 2012 9:44 AM
> To: 'HTTPAPI and FTPAPI Projects'
> Subject: RE: ContractFilter mismatch
>
> The web service is from a 3rd party and I will have to get a hold of
> them to see about any restrictions on the WSDL.
> I have attached the debug log and a screenshot of the http log from
soapUI.
>
>
> -----Original Message-----
> From: Scott Klement [mailto:sk@xxxxxxxxxxxxxxxx]
> Sent: Wednesday, February 15, 2012 6:07 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: ContractFilter mismatch
>
> Hi Ken,
>
> Your WSDL link does not work. I suspect this is something that is
> restricted? I need that in order to know what the SoapAction is
> supposed to look like.
>
> I see that you've enabled debug via the http_debug(*on) call. Can you
> send us the debug file that it creates? That might provide some clues?
>
> At the moment, I don't feel like I have any information to go on.
>
>
>
> On 2/15/2012 6:05 PM, Ken Kantorowicz wrote:
>> I am able to use soapUI to call the web service correctly. When I
>> use the RPG program I get `500 internal server error'.
>>
>> I'm pretty sure it has something to do with the SOAPAction. Here is
>> the information and test program I am using.
>>
> ----------------------------------------------------------------------
> - 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
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------