Request Entity too large

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

Home / Forums / Developers (Apps and Integrations) Forum / Search & Navigation /

Request Entity too large

Fang Huang

Vote:

expand_less 0 expand_more

Hello the magic Forum,

What does this error info means from the log:-- An exception occured while indexing (Batch): The remote server returned an error: (413) Request Entity Too Large.

Best regards,

/Fang

#177268

Apr 06, 2017 14:15

Daniel Ovaska

Vote:

expand_less 0 expand_more

Does it say what class/method throws this error? Sounds like the search engine is trying to index something big?

Using Find or Episerver standard search service?

#177269

Apr 06, 2017 14:23

Fang Huang

Vote:

expand_less 0 expand_more

Hi Daniel,

Using Find.

when the schedule job runs, it sends content in batches, and a batch cannot be larger than 50MB. I use the following code in the EPIServerFindInitialization.

ContentIndexer.Instance.ContentBatchSize = 8;
ContentIndexer.Instance.MediaBatchSize = 2;
ContentIndexer.Instance.MaxTries = 5;
ContentIndexer.Instance.MinBatchSize = 1;

But I still get the same error message. How I wonder?!

#177271

Apr 06, 2017 15:14

Fang Huang

Vote:

expand_less 0 expand_more

Now I know: the dev indices have a lower limit of 5 MB.

http://antecknat.se/blog/2015/02/23/convention-for-episerver-find-to-ignore-large-files/

#177276

Apr 06, 2017 16:18

Fang Huang

Vote:

expand_less 0 expand_more

#177277

Apr 06, 2017 16:18

error This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.