[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ftpapi] HTTPAPI - Hex characters cropping up in parms for http_url_post_stmf
Here's my hunch... someone defined HTTP_ORIG_SHORTFIELD. You should
never do that, this is only for internal use within HTTPAPI.
Aside from that, I don't know off the top of my head, and I'm not going
to be able to give you more in-depth support as long as you're running
version 1.23 of HTTPAPI. That version is 9 years old, and I cannot
support anything that old. So, if the above guess doesn't help you,
please start by upgrading HTTPAPI. Then, provide details as to how we
can reproduce the problem.
On 6/29/2017 12:40 PM, Craig Mcloughlin wrote:
First off, thanks for providing such a useful tool. I’ve been happily
using it for about 6 years now 😊
Recently I seemed to hit an intermittent issue in using HTTPAPI to
make a post request (taking data from a stream file populated with soap).
One of the areas I spotted while checking into this issue seemed to
stem from some hex data being appended to the beginning of the content
type and SOAPAction parameters for the http_url_post_stmf call.
When I track this in debug I see these hex characters appearing:
My calling program just before the call:
…stepping into to HTTPAPRR4:
Some tricky Hex data has appeared just doing my step-into! Have you
ever seen this before?
I know there is some code floating around to handle larger parameter
lengths for these variables recently plus code to put in default
values when these values are not passed in (we do not pass in
useragent for example), but I’m looking for an pointer on where to
troubleshoot / debug as I can’t see any in-between steps where this
hex is getting included.
Ftpapi mailing list