[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using raw to post data
Mike,
HTTPAPI is sending your data. After it is sent, the HTTP server is
supposed to send back a reply like "200 OK" or "500 Internal Server
Error" or "404 Not Found" or something like that. This reply should
subsequently be followed by headers and a response document. (Even upon
error there should be a response document.)
However, it is not replying at all. It is simply disconnecting.
HTTPAPI doesn't know why it's doing that, or what the error should be so
it should says "end with err".
As for what's causing this, it's awfully hard to say. It's possible
that the server thinks you're an imposter (possibly based on how your
data was sent?) so it disconnects you? Or it's possible that there's a
bug in the server somewhere? Hard to say, since it doesn't provide any
feedback about what's wrong.
-SK
On 2/27/2015 12:19 PM, Michael Ryan wrote:
Well, it made sense to take it out the CONNCLOSE additional header...I
need to wait until the user does something...still getting the same
error though. Here's the latest debug log.
On Fri, Feb 27, 2015 at 1:15 PM, Michael Ryan <[1]michaelrtr@xxxxxxxxx>
wrote:
Hmmm...I'll take that out and see what happend. Thanks Mike.
On Fri, Feb 27, 2015 at 1:11 PM, Mike Krebs
<[2]mkrebs@xxxxxxxxxxxxxxxxxx> wrote:
Some of the things you see in the debug are in fact the headers that
are being sent and Content-Length is one of them. I didn't count the
bytes but 140 seems about right.
The recvresp(): end with err is new one for me. I am used to seeing
something more descriptive there. I wonder if that is related to
Connection: close being sent.� That doesn't seem right to me.
-----Original Message-----
From: [3]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[4]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Michael Ryan
Sent: Friday, February 27, 2015 11:41 AM
To: HTTPAPI and FTPAPI Projects
Subject: Using raw to post data
I've modified an existing program to talk to a device. I know I'm
hitting it - I can see the device light up. But I don't get a valid
response - seems like it's an error. I've attached the debug log...can
anyone shed any light? The vendor suggested that content-length wasn't
being passed. I can't see the actual headers in the debug log, but the
log certainly indicated content-length was passed. Thanks!
-----------------------------------------------------------------------
This is the FTPAPI mailing list.� To unsubscribe, please go to:
[5]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
References
1. mailto:michaelrtr@xxxxxxxxx
2. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
3. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
4. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
5. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------