Downstream HTTP header limits? #1675
Labels
needs feedback
Issue is waiting on feedback before acceptance
needs validation
Issue has not been replicated or verified yet
question
Initially seen a question could become a new feature or bug or closed ;)
waiting
Waiting for answer to question or feedback from issue raiser
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: