Re: [lwip-users] heap problem with chrome

[Noam Weissman]

Hi,

 

I am not familiar with netconn API but I will try..

 

Every browser implements the protocol a bit differently. The data fields in the HTTP may not be

In the same order and sometimes (IE) are very long… That leads to problems when your code

Is very optimized and unexpected.

 

I found that on the hard way when I was working on HTTP myself. Use Wireshark and maybe

debug printouts in your own code to see what is the difference.

 

I suggest using the RAW API HTTP server as it is used by many programmers.

 

BR,

Noam.

 

From: lwip-users [mailto:lwip-users-bounces+address@hidden On Behalf Of Mohamed Hnezli
Sent: Wednesday, March 22, 2017 10:42 AM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] heap problem with chrome

 

hello again,

I am using HTTP server example using the netconn API,

I have a strict memory constraint but what makes me confused

is that there is no problem with firefox

 

 

On 21 March 2017 at 18:44, address@hidden <address@hidden> wrote:

Mohamed Hnezli wrote:

when reloading a tab in chrome or adding new one the server crashs. Note
that the server runs well with firefox.
Any help please ?

Last time I tested those two browsers, chrome used more simultaneous connections to my server than firefox. That explains the difference. Your server shouldn't crash though. That's a bug in your port or application and you should fix it :-)

Simon

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

--

            Mohamed HNEZLI

Computer Science Engineer Student

              NSCS_Tunisia