Re: SV: HTTP/1.1 500 Internal Server Error - ContractFilter mismatch

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

hi Magne,

I don't understand your point?  The WSDL file lists the SoapAction as 
starting with https://.   You could complain that the WSDL is wrong -- 
but that's not in David's control.

But, if the WSDL says it starts with https://, then David *must* provide 
the same string when he calls it, otherwise it won't work!

What difference does it make whether the SoapAction starts with 
https://?  As the SoapAction is merely an identifier (no actual network 
communication is done to the URI in the SoapAction) I don't see why it 
matters to you.  The SoapAction could be BobsYourUncle://blah.com and it 
should still work -- as long as it matches the WSDL.


On 1/10/2011 2:49 AM, Magne Kofoed wrote:
> Hi,
>
> are you really using ssl?
> The soap action uses https, but your end-point url has http.
> There is no https init in the log file.
> Or am I missing something here?
>
> Best regards,
> Magne
>
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------