Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-1880

Request entity too large issue when passing around matchmaker input data

    XMLWordPrintable

    Details

      Description

      When working on the inverse transformations, I've implemented a full read of the solutions registry (ie. solutions registry entries for all platforms) as part of the solution registry .get call. This was used for inferring common terms, added to the general payload for the matchmakers. It is quite a bit of data, and when this entire 'matchMakerInput' payload was sent to the matchmaker, it resulted in the following error

      <code>

      {"isError":true,"message":"request entity too large while executing HTTP POST on url %matchMakerPath/match","expected":243468,"length":243468,"limit":102400,"status":413,"type":"entity.too.large"}

      </code>

      For now, this issue has been solved by simply deleting the full solution registry from the payload once it's been used for calculating the inferred common terms. But in the long run, we'll probably need to take this into account and do some filtering of the various payloads and watch how much data we're passing around. Also, we could bump the data max size. See http://stackoverflow.com/questions/19917401/node-js-express-request-entity-too-large

        Attachments

          Activity

            People

            Assignee:
            jhernandez Javier Hernández
            Reporter:
            kasper Kasper Markus
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: