-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Downstream HTTP header limits? #1675
Comments
Hi Mortana!
Could you upgrade your solution to v19 for .NET 7 please?
Everything is possible! 🤣 I guess Ocelot as a ASP.NET API app follows and uses a standard settings for
Please, show your solution and/or at least configuration code!
Please, provide complete call stack information, and error message for sure! Finally,Is this a bug or feature issue? |
Do you use this Kestrel server property? |
Expected Behavior / New Feature
We have configured Kestrel both on our gateway microservice and downstream services to accept header sizes up to 64Kb.
We should be able to send our GET request which contains a large continuation token, to these downstream services.
However, we notice that, we are able to enter middleware in our gateway, but the moment we run the ocelot middleware, we receive a 400 headers too large.
When we try to send the same call to the individual microservice directly, we receive a successful response, so I'm thinking Ocelot is not adhering to the limits for some reason, when replaying the HTTP request to a downstream service.
Is that possible?
Some information:
The text was updated successfully, but these errors were encountered: