The 201 responses are closed prematurely on resumable uploads about nginx-upload-module HOT 4 CLOSED

This happens when the actual length of body is larger than the length declared in Content-Length request header.

from nginx-upload-module.

Hi Vladimir,

Yes, you are absolutely right, I was not using the PHP Curl library properly (trusting CURLOPT_INFILESIZE to
stop sending data instead of using a CURLOPT_READFUNCTION callback and managing that myself). Anyway,
it now works properly (I removed the CURLOPT_VERBOSE option for clarity) :

201 -> 0-262118/1800417
201 -> 0-524237/1800417
201 -> 0-786356/1800417
201 -> 0-1048475/1800417
201 -> 0-1310594/1800417
201 -> 0-1572713/1800417
200 -> stdClass Object
(
[format] => Flash Video
[acodec] => MPEG Audio
[vcodec] => H.263
[duration] => 30320
[bitrate] => 475044
[dimension] => 320x240
[name] => infile
[size] => 1800417
[url] => http://localhost/files/8dcbee8592e4f2f6f8b410e2e11ac00b.flv#c2VhbD02Yzg5ODc5ODMwMjY3YmE5ZGU2Y2Q1MTM4OTBjZDE5MyZmb3JtYXQ9Rmxhc2grVmlkZW8mYWNvZGVjPU1QRUcrQXVkaW8mdmNvZGVjPUguMjYzJmR1cmF0aW9uPTMwMzIwJmJpdHJhdGU9NDc1MDQ0JmRpbWVuc2lvbj0zMjB4MjQwJm5hbWU9aW5maWxlJnNpemU9MTgwMDQxNyZoYXNoPTlhYjA0MjZhY2U5ODRmNGEzZjdjNGUwODZiNmI2ZDNlNGE5M2ViM2Q=
[hash] => 9ab0426ace984f4a3f7c4e086b6b6d3e4a93eb3d
[seal] => 6c89879830267ba9de6cd513890cd193
)

However, don't you think those strange messages in the error log are an indication of a potential memory corruption,
and that the module should be amended to address a potential DOS issue?

Thanks,
Pierre-Yves

from nginx-upload-module.

No, this is not an indication of a memory corruption, it's just the data of the request body interpreted as HTTP request. Furthermore, this message is produced by nginx and the module has not influence on it.

from nginx-upload-module.

Understoud, thx again!

from nginx-upload-module.