When TLS is enabled recieved and size are always the same
Vespasian opened this issue · comments
After I setup TLS for my website the size and the recieved field in the reported progress are always the same (the correct size of the uploaded file). I tested it with large files to make sure the upload doesn't finish to early
The state still changes from uploading to done once the upload finishes.
Using standard unencrypted http everything works as expected.
I configure TLS with the following directives
ssl_certificate /etc/ssl/private/certificate.pem;
ssl_certificate_key /etc/ssl/private/certificate.key;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS !RC4";
add_header Strict-Transport-Security "max-age=31536000; includeSubdomains;";
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 10m;
A debug session for one file upload is here
https://gist.github.com/Vespasian/d2214d1c25544510f58d
If you need anything feel free to contact me by mail or in this issue. Thanks for your great work on this module
@Vespasian, I quickly read you log searching for "upload", and I couldn't find any spot where the upload is actually posted to nginx. There are indication that some older uploads are being deleted from the known upload database, but nothing about new uploads.
Can you check your whole configuration to make sure you have debug enabled everywhere it's needed?
Then, send again the error log. The part I'm interested in is the the beginning of the upload.
I'll create a minimal configuration, which provokes the bug, later this week and send you the logs once I manage to find something about the start of the upload in them.
@Vespasian would you have a log file showing the problem with and without TLS activated?
I'll try to debug the issue during the week, but apparently you're not the only one having the issue (see issue #32) with TLS enabled.
This isn't TLS specific, as I was able to reproduce it without TLS enabled.
This is a duplicate of #36.