You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Viewing in Javascript console shows that the attempt to POST /prod/admin/catalog/visibility fails with an uncaught 413 status:
PayloadTooLargeError: request entity too large at IncomingMessage.onData (/var/task/node_modules/raw-body/index.js:246:12) at emitOne (events.js:116:13) at IncomingMessage.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at IncomingMessage.Readable.push (_stream_readable.js:208:10) at HTTPParser.parserOnBody (_http_common.js:139:22)
I can provide a 330K example file if needed, but I expect any large file upload will break it.
The text was updated successfully, but these errors were encountered:
same issue for me. File size is 167kb, will be 350kb when done.
did some research and then reduced the file size to be just under 128kb and it loads just fine. so that eliminates a badly formatted file (mostly), or corrupt file.
*** edit this problem is ocurring when I try to load a yaml file
did some more research and I undertsand the AWS API gateway has a 128kb limit when using websockets. Is limit in play here? have I mucked up something fundamental.
Trying to add a generic API:
Results in a greyed out upload UI and no message.
Viewing in Javascript console shows that the attempt to
POST /prod/admin/catalog/visibility
fails with an uncaught 413 status:I can provide a 330K example file if needed, but I expect any large file upload will break it.
The text was updated successfully, but these errors were encountered: