Thanks for your reply c g.
I think IE does work better after some trials. However, the issue is still there when I have say 3 tabs open and refresh one of the tab, then the http server just stops responding to any requests, tho the accept() are still looping with timeouts.
I think it has more to do with "wiced_tcp_receive()" hang up issues that have been reported on NetX_Duo....
Not sure using LwIP would help, but at least we have the source code.
Also, I find it a abit weird that listen and accept uses same socket...
Can you please create a new discussion if there is a new question?
However, the original question "HTTP server locks up with multiple requests" still persists.
Just wondering if you have experienced this when running the "snip/ping_webserver example".
Having multiple browser tabs opened and connected to the HTTP server on the target.
(at the same time, refreshing some of the tabs) eventually will cause the HTTP / TCPIP to lock up.
I tried doubling the "NETWORKING_WORKER_THREAD_QUEUE_SIZE" from 15 to 30 today which seemed to have helped the performance and no lock up have occurred so far. But not sure if this is the ultimate solution.
I am using the ISM4319_TESTBOARD as a server and I have the same problem, in my case, my server is locked up after a client device connects and disconnects several times from the access point. I think the problem is that the server does not detect the disconnection of the client and each new disconnection and reconnection to the access point, it takes it as a device more connected to the network.
Could you help me solve this problem?