[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SOAPAction Expansion Issues (HTTP_ORIG_SHORTFIELD Logic Seems Flawed)
Ron,
I'm sorry, I don't agree with you. I think your result is truncated to
2A because you removed the /define HTTP_ORIG_SHORTFIELD that I
deliberately hard-coded into the program.
For me, HTTPAPI 1.24 works with SoapAction values up to 16384 without
having to do _anything_ to the defines/undefines.
Seems to me that you are breaking it by changing the defines/undefines
that I put in there. And since you've broken it, you are now finding
different ways to fix it... which will eventually prevail, but will
break backward compatibility.
On 4/18/2011 1:03 PM, Ron wrote:
>
> A little further testing and research and I believe I have discovered
> the issue. You used the following declarations code to allow for your
> "tricky" technique.
>
> D getSA PR 16384A varying
> D ExtProc('GETREALSA')
> D peSoapAction 2a const
> D getRealSA PR 16384A varying
> D peSoapAction 2a
>
> Since the constant parameter was only defined as 2A anything passed
> that point was being truncated. I changed that code to
>
>
>
> D getSA PR 16384A varying
> D ExtProc('GETREALSA')
> D peSoapAction 16384a Const
> D getRealSA PR 16384A varying
> D peSoapAction 2a
>
> and that seemed to address the truncation issue. I admit I rushed
> through this change as I have people waiting on this but I think the
> fix was a proper one.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------