Forum

Upload fails when using ssl

AntiLarsson
26 December 2015, 20:40
Hi,

I have a problem with my webserver. When I try to upload a file I get 413 Request Entity Too Large when using https but when I use http everything works as expected. My MaxRequestSize is 1536000 which should be more than enough. I can't figure out what the problem is so any pointers would be appreciated.

Regards
AntiLarsson
AntiLarsson
26 December 2015, 20:43
Debian 8 and Hiawatha 10.0
Hugo Leisink
28 December 2015, 17:02
Huh? That's weird. Hiawatha doesn't make any difference between HTTP and HTTPS when it comes to such settings. MaxRequestSize is the same for both HTTP and HTTPS. I have no idea what went wrong...
AntiLarsson
29 December 2015, 21:25
I get a "Secure Connection Failed" message when I try the operation in firefox and the 413 in Chrome. If I upload a file that is small 4kb everything works as expected both in FF and in Chrome. The request that fails is a POST request. This error started when I enabled ssl with a certificate form letsencrypt.
AntiLarsson
31 December 2015, 00:41
Any ideas on how to investigate the problem?
Hugo Leisink
31 December 2015, 09:59
No, not really. I often upload large files (several tens of megabytes) via HTTPS myself. So, all I know is that it does work. I've been thinking about this, but I don't understand why it goes wrong. These kind of limitations have nothing to do with TLS or no TLS. TLS is just a connection parameter in Hiawatha, nothing more.

What kind of application do you use to handle the upload? Could it be that the problem lies there?
AntiLarsson
7 January 2016, 01:07
I have tried a file upload with a simple upload script and it seems to work in Chrome. When I try it in my application I get a 413 which seems odd. Do you have any idea on how my script is able to trigger this error? When I inspect the source nothing fancy seems to go on so I'm kind of stuck.

When using FF i still get the "Secure Connection Failed". I'm have never used https before so I can't really figure out whats wrong.
Hugo Leisink
7 January 2016, 13:37
That proofs that the cause of your issue lies in the application. I have no idea what that might be.

About the TLS error, that could for example a root-certificate issue (not installed in FF) or a cipher preference issue. As I can't see inside your server or browser, I don't know what causes it.
This topic has been closed.