[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: HTTP 200 return code



Barry,

Nothing in particular to offer from here. It sounds like you've been deeper
in the programs than I.

Did you see all the bytes come across but just not get written? Or did the
program stop processing the incoming data?

Was the data you did receive correct (particularly around the 32k breaks but
also at the packet level (probably around 14-1500 bytes))?

Mike Krebs  

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Barry Shrum
Sent: Friday, December 14, 2007 8:38 AM
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Subject: HTTP 200 return code

Good morning,

I posted this a couple of weeks ago but haven't heard a response so I
thought I'd repost in case it was missed.

Thanks,

Barry

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Barry Shrum
Sent: Friday, November 30, 2007 4:06 PM
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Cc: Candace Marquardt
Subject: HTTP 200 return code


Hi,

We have a trading partner that has special processing if a response from
them will be greater than 32K.  The first 7 bytes of a response is the
number of bytes returned in the response, no inclusive of the 7-byte
counter.  If a response is greater than 32K, it is sent in 32K pieces.
Using debug, it seems that return code 100 is returned for all but the last
section, which has return code 200.

Unfortunately, there is very limited test data available.  I have two
requests I can make - one that returns 50,812 bytes and one that returns
106,344.  The first one works fine - the last section returns a code 200 and
the entire response is written to the IFS file.  The second one only writes
95,263 of the 106,344 bytes to the IFS file.

It appears that the process works if there are two pieces to the response,
but not if there is four.  However, 95,263 is not exactly 32K three times,
either.  I followed the debug through until the field rc had a value of 200,
then it returned and RecvDoc was called which created the IFS file with the
truncated response.

I attached two debug files.  http_debug_good.txt is the for the successful
response and http_debug_bad.txt is the unsuccessful one.  I removed some
information to maintain confidentiality with our trading partner.  Lines I
changed are marked with "*** " and " ***" before and after.

Any suggestions would be quite welcome.

Thanks,

Barry Shrum

--
This message has been scanned and appears to be clean.


-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------