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

Make the read and write buffer sizes for the requests handled, respectively responses created by heimdall configurable #704

Closed
3 tasks done
dadrus opened this issue Jun 23, 2023 · 0 comments · Fixed by #706
Labels
feature Used for new features
Milestone

Comments

@dadrus
Copy link
Owner

dadrus commented Jun 23, 2023

Preflight checklist

Describe the background of your feature request

As of today, the read and write buffer sizes for the requests are set to 4k (the default used by fasthttp used by heimdall for HTTP handling). If the requests sent to heimdall, or the response generated by heimdall exceed these limits, the connection will more or less silently fail.

Describe your idea

Make the buffer sizes configurable

Are there any workarounds or alternatives?

Reduce the sizes of the requests, which is hardly possible

Version

v0.8.2-alpha

Additional Context

No response

@dadrus dadrus added the feature Used for new features label Jun 23, 2023
@dadrus dadrus added this to the v0.9.0-alpha milestone Jun 23, 2023
@dadrus dadrus changed the title Make the read and write buffer sizes for the requests handled by heimdall configurable Make the read and write buffer sizes for the requests handled and responses created by heimdall configurable Jun 23, 2023
@dadrus dadrus changed the title Make the read and write buffer sizes for the requests handled and responses created by heimdall configurable Make the read and write buffer sizes for the requests handled, respectively responses created by heimdall configurable Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Used for new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant