Aparajita Fishman wrote:
Through a lot of trial and error I'll report that changing:
$err:=ITK_TCPRcv ($streamRef;$headerTxt;32000;0;0;<>CRLF+<>CRLF;2*60) `Grab the header...
to
$err:=ITK_TCPRcv ($streamRef;$headerTxt;1024;0;0;<>CRLF+<>CRLF;2*60) `Grab the header...
appears to have a positive affect.
FWIW, I had used 32000 as a conservative measure not knowing how large incoming request headers might be. Therefore, this "fix" does have the potential to break in the future.
I can't see how _headers_ would ever be more than a few K. Headers are just that...headers. There isn't much data in them.
Thanks for the clarification. I suspected this but wasn't sure. I just reread relavant parts of RFC 1945 (ftp://ftp.rfc-editor.org/in-notes/rfc1945.txt).
In testing this change against all of the forms in our system I've been logging the header sizes. All headers have been in the ~350-700 byte range. My point was that I need to be aware that my selected MaxLen parameter value could be too small if future Active4D pages are implemented that result in a header larger than that value.
Therefore I will:
1) Make the maxlen parameter value configurable so I won't have to recompile if I need to increase it.
2) Install code into A4D_PreStreamExecuteHook that allows me to write header info to the Active4D console if I need to see what is going on.
best,
Brad
_______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
