Hi Tomas,
> I see, so it looks like some kind of mismatch between chunked and
> non-chunked mode used by the web server and expected by the client
> script. I'll have a look into it. nginx probably messes that up.
I'm not sure whether it is relevant here, but I know of another
(similar?) phenom
Hi Alex,
>> I see, so it looks like some kind of mismatch between chunked and
>> non-chunked mode used by the web server and expected by the client
>> script. I'll have a look into it. nginx probably messes that up.
> To be precise, that message is "1^M^JT^M^J0^M^J^M" (see line 154 of
> "lib/fo
Hi Tomas,
> I fixed lib/form.l which is attached. The problem was that chunking
> was hardcoded in the form.l code limiting it's usability to http1.1.
> However, nginx proxy implements http1.0 only. The fix makes form.l
> usable with both http1.0 and http1.1.
Many thanks, good idea!
I incorpor
Hi Tomas,
> However, nginx proxy implements http1.0 only. The fix makes form.l
The restriction to HTTP/1.0 has another disadvantage: It will degrade
the performance of XMLHttpRequests, because it needs to open and close a
separate TCP connection for each HTTP transaction. Certain operations,
lik
Hi Alex,
> The restriction to HTTP/1.0 has another disadvantage: It will degrade
> the performance of XMLHttpRequests, because it needs to open and close a
> separate TCP connection for each HTTP transaction. Certain operations,
> like scrolling in charts, are perceptibly slowed down, especially w