TCP Connection

Giulio Loffreda giulio at loffreda.com.br
Fri Mar 4 16:41:42 UTC 2016


Thank you for your answer.

Here is my log after the request, my request, my response and my nginx.conf

root at vps190138:~# cat /var/log/nginx-error.log
2016/03/04 15:49:02 [notice] 8990#0: using the "epoll" event method
2016/03/04 15:49:02 [notice] 8990#0: nginx/1.8.1
2016/03/04 15:49:02 [notice] 8990#0: OS: Linux 3.13.0-66-generic
2016/03/04 15:49:02 [notice] 8990#0: getrlimit(RLIMIT_NOFILE): 1024:4096
2016/03/04 15:49:02 [notice] 8991#0: start worker processes
2016/03/04 15:49:02 [notice] 8991#0: start worker process 8993


#REQUEST
AT+CIPSTART="TCP", "myhost.com","80"
AT+CIPSEND=150 

POST /devices/deviceRegister HTTP/1.1
Host: myhost.com
Cache-Control: no-cache
Content-Type: application/json
Content-Length:14

{"IMEI":"aa"}



#RESPONSE
SEND OK
HTTP/1.1 400 Bad Request
Server: nginx/1.8.1
Date: Fri, 04 Mar 2016 15:52:21 GMT
Content-Type: text/html
Content-Length: 172
Connection: close

<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.8.1</center>
</body>
</html>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nginx.conf
Type: application/octet-stream
Size: 1625 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160304/e7d89d9c/attachment.obj>
-------------- next part --------------

> Le 4 mars 2016 ? 17:24, Valentin V. Bartenev <vbart at nginx.com> a ?crit :
> 
> On Friday 04 March 2016 17:20:18 Giulio Loffreda wrote:
>> Hi All,
>> 
>> If I?m sending this email to wrong list, apologies and give me the good one.
>> 
>> I have one embedded application which needs to connect via TCP and send an HTTP request.
>> We run Nginx on Ubuntu 14.04.
>> 
>> I can connect and persist, but once the packet is sent, I get HTTP 400 without any log and without web server taking the request.
>> 
>> I think it is a deeper level on Nginx but having hard to find a good answer.
>> 
>> Hope somebody can help.
>> 
> [..]
> 
> The reason of 400 is usually logged on "info" level in error_log.
> 
> See: http://nginx.org/r/error_log
> 
>  wbr, Valentin V. Bartenev
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx



More information about the nginx mailing list