• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 748 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Connected LaunchPad enet_io I/O Control Demo1 missing HTTP response headers

Dan K
Expert 1210 points

I am no expert on HTTP, but when I run the "enet_io" demo application for the Connected Launchpad, I noticed (using Wireshark) that HTTP response headers are not sent when running I/O Control Demo 1 (HTTP Requests) and clicking on the Toggle LED and Set Speed buttons. The demo appears to work as expected in my browser (Firefox), but isn't this a violation of the HTTP protocol?

In looking at the LWIP file "httpd.c", function "get_http_headers()", this appears to be on purpose, as indicated by the following code comment:

    /* Does the URL passed have any file extension?  If not, we assume it
       is a special-case URL used for control state notification and we do
       not send any HTTP headers with the response. */

But again I question whether this is standard practice for HTTP control applications?

Thanks,

Dan