🐛 airbyte-proxy: Fix 413 Request Entity Too Large nginx/1.23.2 for Airbyte > 0.40.15 #20383
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
From issue #18822
For long schemas creating the connection fails due to the request payload being over
1M
. This issue was introduced with the new airbyte-proxy service asclient_max_body_size
clause is not set on nginx template and defaults to1M
limit.How
adding
client_max_body_size
clause to replicate the one set onairbyte-server
nginx.🚨 User Impact 🚨
No breaking changes
Pre-merge Checklist
Expand the relevant checklist and delete the others.
BugFix of service
Community member or Airbyter