Xiang Xiao, Thanks for the PR, I updated to the latest master since this has been merged, and I tried it. I am getting a different error now:
* Closing connection 0 curl: (18) transfer closed with 226 bytes remaining to read I tried removing CONFIG_NET_TCP_READAHEAD from my config too, with the same result. It looks like the connection is now being prematurely closed, rather than not being closed at all. Do you have advice on how to fix this? Or where to look? cheers adam On Sat, Jan 11, 2020 at 12:08 AM Xiang Xiao <xiaoxiang781...@gmail.com> wrote: > On Sat, Jan 11, 2020 at 12:42 PM Adam Feuer <a...@starcat.io> wrote: > > > > After debugging, it seems like the TCP connection is not being closed > > correctly, and the client receive times out. > > > > Could this be the TCP close problem that has been reported? When was it > > introduced? I'd like to go back to a previous version and see if that > works > > correctly. > > > > Yes, Rob report the same issue here: > https://groups.google.com/forum/#!topic/nuttx/nF0pfDkd3hA > The fix is here: > https://github.com/apache/incubator-nuttx/pull/76 > Please try it. > > > -adam > > > > On Fri, Jan 10, 2020 at 16:32 Adam Feuer <a...@starcat.io> wrote: > > > > > Hi, > > > > > > I got the uIP webserver example to work on the SAMA5D36-Xplained. > However, > > > it's not fast enough for my needs. (Probably to be expected since it's > > > designed for low-power devices.) > > > > > > I am trying to get the thttpd example to work. It compiles, and I can > run > > > the thttp command from the NuttX shell. It will serve about 75% of the > > > index page, and then appears to hang– the page never finishes > transmission. > > > I'm going to debug, but I thought I'd ask: > > > > > > Has anyone seen this before? If so, what's wrong and how do I fix it? > > > > > > cheers > > > adam > > > -- > > > Adam Feuer <a...@starcat.io> > > > > > -- > > Adam Feuer <a...@starcat.io> > -- Adam Feuer <a...@starcat.io>
