Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

Requirements:
Jira Legacy
server

...

System JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId

...

01505d01-

...

b853-

...

3c2e-

...

90f1-

...

ee9b165564fc
keyMODINVOICE-125

A solution for enforcement a size limit for invoice documents should be developed.

...

But! From the RMB code:

// IMPORTANT!!!
// the body of the request will be read into memory for ALL PUT requests
// and for POST requests with the content-types below ONLY!!!
// multipart, for example will not be read by the body handler as vertx saves
// multiparts and www-encoded to disk - hence multiparts will be handled differently
// see uploadHandler further down

This means that we can't solve OOM issue if file size is larger that module heap size. 

...

Application/octet-stream mechanism allows to control sending request size in the following manner. For this approach we need to know approximate size of json request content size, metadata and Base64-encoded file size (original invoice document size (file size) + 30%). For example, file limit is 10 Mb, other json content size is 1 Mb. As a result MAX_DOCUMENT_SIZE limit parameter should be approx. 14Mb. This looks not so precise but should be enough for request size control.

...