Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Request Header Fields Too Large" when calling management api multiple times #18

Open
sdm7306 opened this issue May 25, 2023 · 2 comments

Comments

@sdm7306
Copy link

sdm7306 commented May 25, 2023

I am writting my own bulk operations script to mass update and publish our contentstack entries via the management API.

The sdk throws a ContentstackException when attempting to call the management api multiple times with a "Request Header Fields Too Large" error message. I am dealing with a couple thousand entries and it always seems to start failing on the 1271st call to the API.

at Contentstack.Management.Core.Http.ContentstackHttpRequest.GetResponse() at Contentstack.Management.Core.Runtime.Pipeline.HttpHandler.InvokeSync(IExecutionContext executionContext) at Contentstack.Management.Core.Runtime.Pipeline.RetryHandler.RetryHandler.InvokeSync(IExecutionContext executionContext) at Contentstack.Management.Core.ContentstackClient.InvokeSync[TRequest](TRequest request)

I was able to get arround the error by creating a new client instance for every single call which is not ideal.

I am using .NET 6 with contentstack.management.csharp" Version="0.1.0"

@ishaileshmishra
Copy link
Contributor

Thanks for reaching out, @sdm7306. We appreciate you bringing this issue to our attention. Our team will investigate the problem you encountered with the Contentstack SDK when making multiple calls to the management API, resulting in a 'Request Header Fields Too Large' error message.

We will work on fixing the issue and, if necessary, provide you with an updated build that addresses this problem.

Thank you for your understanding

@lauerya
Copy link

lauerya commented Oct 6, 2023

+1, we are experiencing this same issue. Each request is appending the Accept header with "image/jpeg" which eventually causes this error to be thrown.

Is there any update on this issue? Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants