[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] Serving httpd files sequentially

From: Marshall Brown
Subject: [lwip-users] Serving httpd files sequentially
Date: Tue, 2 Apr 2013 08:42:41 +0000

Hi there


I have LWIP 1.4.1 successfully running on an LPC1768 with no OS, I have used the upper 32 of RAM (of a total of 64k) for LWIP with the following options set (check the attached lwipopts.h for further settings)

#define MEM_SIZE                    (31 * 1024)

#define MEMP_MEM_MALLOC             1     //MKB added to try and clean up the memory a bit


My understanding of the above define “MEMP_MEM_MALLOC” puts everything on the heap, which is fine for my application


I am trying to serve a standard web page from an SD card, the page has links to 3 or 4 image files. I’ve tried so many versions of contrib httpd and they all come unstuck when the browser requests “GET /file 1” followed by “GET /file 2” when LWIP is still serving or ACK the first file. I’m not sure if it is a function of LWIP or the SD card (EFSL) that is not happy, but the files are coming out corrupted.



I would like to know if there is a way to prevent the browser from requesting a file before the web server has finished serving the previous one? I have tried the following options (as well as MANY others)

#define TCP_LISTEN_BACKLOG          1     //Default = 0 == off 0 means "disabled". In this case, backlog is limited by the number of PCBs.

                                                              //this means we use all our memory up accepting listening pcb's then can't service them so we limit to 1




But the PCBs remain in the CLOSE-WAIT state for such a long time they can’t be reused.


The screen shot below shows the files being served and the subsequent corruption. Any help would be appreciated.








Attachment: Marshall Brown.vcf
Description: Marshall Brown.vcf

Attachment: lwipopts.h
Description: lwipopts.h

Attachment: web_capture.pcapng
Description: web_capture.pcapng

reply via email to

[Prev in Thread] Current Thread [Next in Thread]