1 Reply Latest reply on Dec 9, 2015 11:54 AM by abirjepatil

    tcp_receive

    mcarp

      I have an application that gets a response from the server that looks like, "HTTP/1.1 200 OK

      Transfer-Encoding: chunked

      Date: Thu, 26 Nov 2015 01:13:12 GMT"

       

      Standard stuff, really. I moved from WICED 2.4.0 to 2.4.1 (old, I know, ignore that for the moment) and now, about half the time the first call to wiced_tcp_receive() returns just "H" and then the second returns all the rest, starting with "TTP..."

       

      I could hack in a bunch of code to combine the packets, but this wasn't happening on 2.4.0 and I don't want to deal with a lot of corner cases that might arise.

       

      Any ideas?

        • 1. Re: tcp_receive
          abirjepatil

          Hey,

           

          I did see the same behavior with a BCM943362 and WICED SDK 2.4.1.

          The issue has been resolved in later versions.

          I assume that you are trying to get a HTTP response from the server.

          In that case, the https_client application would be the right thing for you to look at.

           

          I tested the https_client application with  WICED SDK 3.4.0 to get a response from the server.

          The app gets a response from https://www.google.com and prints it on the console.

          The response that I got is:-https_resp.png

           

          Hope that solves your problem.

           

          Best Regards,

          AB