We're getting ready to upgrade a V11-based system to v14.2 with Active4D 6.1. We use NTK for the web server.
I'm occasionally seeing "Connection Reset" errors when serving Active4D pages. I have not followed this thread closely, but would your recommendation "Removing that block of code turns out to be the right thing" help? If so, what/where is that "block of code"? Thanks, Brad Perkins On 10/18/14 6:17 PM, "Aparajita Fishman" <[email protected]> wrote: >> I¹ve used both WEB SEND RAW DATA and WEB SEND BLOB. The browser hanging >>isn¹t caused by either of those two commands, it¹s caused by the >>³Connection Close² field in the response header. When I remove that >>block of code, it stops hanging. > >Removing that block of code turns out to be the right thing. > >No Content-Length header was generated when the status was 304 (Not >Modified), which falsely triggered the adding of "Connection: close". > >In any case, I looked at the way real web servers (apache, nginx) handle >304 responses, and they do not use "Connection: close". So lines 84-96 of >A4D_OnWebConnection (starting with the comment "//HTTP 1.1 spec says..." >along with the entire following If block) should be removed entirely. > >Regards, > > Aparajita > >_______________________________________________ >Active4D-dev mailing list >[email protected] >http://list.aparajitaworld.com/listinfo/active4d-dev >Archives: http://active4d-nabble.aparajitaworld.com/ > _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
