Re: HTTP 200 return code

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Barry,

I'm sorry -- I thought I already replied to this??

I completely agree with Ian's analysis of this.  The HTTP server you're 
connecting to is sending the following 'Content-length: 95270'.  This 
number isn't decided upon by HTTPAPI -- it's sent to HTTPAPI by the 
server you're connected to.

You say that you only receive 95263 bytes, plus the 7 byte counter. 
Guess what?  95263+7 = 95270.  That's exactly what the server told 
HTTPAPI that it was going to send.  HTTPAPI can't receive data that 
hasn't been sent.

I'm scratching my head trying to think of a reason why the application 
would send a higher number than the number of physical bytes, but I'm 
having a hard time coming up with anything other than "the application 
is wrong."   Maybe the server is giving you a count of the number of 
bytes in UTF-8 format, and then is converting to ASCII (this changing 
the count) before sending it?


Barry Shrum wrote:
> 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
> 
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------