Why does Jira server reset connection when uploading attachment larger than upload size limit?

[AutomationUIUser]

I had set upload  size limit of 10MB and tried adding a file of 41 MB however, instead of providing a response with suitable error code the jira server resets the connection.

For more details please take a look at attached screenshot.

However when the attachment size is less than 10MB it responds correctly.

[Andy Heinzer]

Hi,

Sorry to hear about this problem here.  I can see that you're using Postman to try to make a REST API call to Jira Server in order to upload an attachment file, but that this process is not providing a response when the file exceeds Jira's set limit.

I tried to recreate this problem in my latest Jira 8.7.0 version, however when I tested this I get back a 404 error as expected for files that exceed the set limit:

user$ curl -D- -u username:password -X POST -H "X-Atlassian-Token: no-check" -F "file=@IMG-1052.MOV" http://localhost:8870/rest/api/2/issue/DESK-36/attachments
HTTP/1.1 100

HTTP/1.1 404 
X-AREQUESTID: 850x1416x1
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: frame-ancestors 'self'
X-ASEN: [redacted]
Set-Cookie: JSESSIONID=[redacted]; Path=/; HttpOnly
X-Seraph-LoginReason: OK
Set-Cookie: atlassian.xsrf.token=[redacted]; Path=/
X-ASESSIONID: [redacted]
X-AUSERNAME: username
Cache-Control: no-cache, no-store, no-transform
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 05 Feb 2020 20:10:01 GMT
Connection: close

The field file exceeds its maximum permitted size of 10485760 bytes.

So right now, I'm not sure why your REST client is not returning this same kind of error message.  I would like to learn more about your environment so that we can troubleshoot this behavior further.  Could you let me know:

1. What version of Jira Server this is?
2. Could we take a look at the headers of your REST call here?  (I don't need to see authorization or sensitive info, just curious if there is some switch there that might be preventing the error response from reaching back to your client in some way)

Interested to learn more about this.

Cheers,

Andy