Re: [lwip-users] Avoid connection close by lwIP server

[Satz Klauer]

OK, to avoid misunderstandigs: I do NOT want to have a
HTTP-connection, I just used this example as starting point and to
test my underlying implementation. Finally the whole thing shall
become a plain TCP/IP connection where client and lwIP-server
communicate with each other over a longer time and where connection is
NOT closed after every response from server.

I know the http-example that comes with lwIP does this in a completely
different way and I have to modify this example. The only thing I want
to know and I did not understand until now: where in this example is
the connection closed?


On Mon, Dec 16, 2013 at 11:22 AM, Sylvain Rochet <address@hidden> wrote:
> Hi,
>
> On Mon, Dec 16, 2013 at 07:41:06AM +0100, Satz Klauer wrote:
>> Hi,
>>
>> I'm currently new to lwIP and so I'm still trying to understand it.
>> Thus I used the httpserver_raw example as starting point for my
>> application.
>>
>> Since I do not need a http-connection which closes socket after every
>> successfull transmission, but a connection where data are exchanged in
>> both directions for a longer until the client drops the connection, I
>> modified the http-example a bit: parsing for "GET /" was removed, data
>> are received permanentely and http_parse_request() generates some
>> test-response.
>>
>> Now http_parse_request() returns ERR_OK but the connection is still
>> closed after transmission of my test data. So my question: where is
>> this planned closing of http-connection done?
>
> You should learn a little bit how HTTP work.
>
> What you actually have to do is adding a HTTP Keep-Alive support, which
> is a bit more difficult than just keeping the TCP connection open :)
>
> See: http://en.wikipedia.org/wiki/HTTP_persistent_connection
>
> Sylvain
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lwip-users