Feature/urlencoded limit#1201
Conversation
Added documentation for koop option `bodyParserLimit` (for POST maximum body size). Also added some unit tests.
🦋 Changeset detectedLatest commit: d6bdd9b The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@anders-kane I noticed that you've been merging some PRs. Can you take a look at this one? |
I will take a look. There is an ongoing effort to transition ownership of Koop to a myself and few other engineers at Esri as it has not been actively maintained for the past couple of years. Hope to improve that over the coming months. |
|
@anders-kane Thanks! I see that some checks failed. Should I take a look and update the PR? UPDATE: I realize there isn't anything I can do (403 error updating coverage report comment). |
See related issue #1200 and #624
This adds documentation for the new Koop constructor options
bodyParserLimitandurlencodedLimit.The ArcGIS SDK for Javascript's FeatureTable submits queries using x-form-urlencoded, and if that string exceeds 100kb, then Koop (express) throws
PayloadTooLargeError: request entity too large.This fixes that. Because this includes the fix for #624, I'll close the other PR unmerged.