This only appears to affect users using 4D's web server. I don't see the method "A4D_OnWebConnection" in our structure. We use NTK.
Thanks, -- Brad On 10/24/14 11:05 AM, "Perkins, Bradley D" <bperk...@lanl.gov> wrote: >Thanks. I see it now. > >-- Brad > > >On 10/24/14 9:09 AM, "Aparajita Fishman" <aparaj...@aparajitaworld.com> >wrote: > >>> what/where is that "block of code"? >> >>Look at the text below a little more carefully, I said exactly what >>method and which lines. >> >> >>>> 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 >>Active4D-dev@aparajitaworld.com >>http://list.aparajitaworld.com/listinfo/active4d-dev >>Archives: http://active4d-nabble.aparajitaworld.com/ >> > > >_______________________________________________ >Active4D-dev mailing list >Active4D-dev@aparajitaworld.com >http://list.aparajitaworld.com/listinfo/active4d-dev >Archives: http://active4d-nabble.aparajitaworld.com/ > _______________________________________________ Active4D-dev mailing list Active4D-dev@aparajitaworld.com http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
