Hi Peter,

there is a bug with truncating HTTP responses in 4D. It's fixed in one of the 
latest nighthly builds.


Peter
  _____  

From: Peter Jakobsson [mailto:[email protected]]
To: Active4D Developer Discussion List [mailto:[email protected]]
Sent: Thu, 16 Oct 2014 02:46:34 +0100
Subject: [Active4d-dev] Adverse Effects of http 1.1 logic without 
'content-length'

Hi
  
  I’m experiencing a situation where the browser “jams” periodically with 4D 
v14 in remote mode. What happens is after 4-5 refreshes in fairly quick 
succession, the request hangs and the browser becomes unresponsive. On 
cancelling the request (i.e. in Safari, clicking the “x” at the end of the URL 
bar) it becomes responsive again and the request can be re-initiated, usually 
successfully.
  
  I traced this to being invoked by the new http 1.1 lines in the Active4D 
shell request handler code - i.e. the part that checks for the presence of the 
“content-length” response header and closes the connection if not present. If I 
remove this block, the request hanging phenomenon disappears.
  
  First of all, I’m wondering is this a feature or a bug ? (The browser 
hanging). Secondly, should we be adding the content-length header 
programmatically into all responses (but what about stuff like scripts and bits 
and pieces of static graphics etc - I won’t be able to cover everything).
  
  Thirdly, can this code block be safely disabled to make the browsing smooth 
again ?
  
  Finally, another new thing that occurs in 4D v14 all the time is that when it 
is shut down, 4D displays a message saying:
  
   “Task http connection handler” and 2 others are still running.
   “To let the application finish its work click ok”
   “To terminate and quit click cancel (You may damage your data)”
  
  Despite this, there are no residual web processes running. Anyone else seen 
this ?
  
  Any light that can be thrown on these issues - much appreciated !
  
  Regards
  
  Peter
  
  P.S. The latest nightly builds are manifesting the “Pragma Cache” response 
bug again because Active4D’s shell thinks they’re outside the scope of “bugged 
versions” for WEB SEND RAW DATA whereas in fact they’re not because 4D haven’t 
fixed it yet but they do seem to have updated the revision number.
  
  _______________________________________________
  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/

Reply via email to