There need to be sane and defensive request size and time limits, and response size and time limits on both the client direction as well as the backend direction. The all of these values must be able to be overridden with environment variables, but the defaults should be same. I believe the same defaults for request should be 60 seconds and perhaps 100 megabytes. And the same defaults for response should be 30 minutes and uh five gigabytes, these are client facing, and then uh similar ones for the backend facing.
There need to be sane and defensive request size and time limits, and response size and time limits on both the client direction as well as the backend direction. The all of these values must be able to be overridden with environment variables, but the defaults should be same. I believe the same defaults for request should be 60 seconds and perhaps 100 megabytes. And the same defaults for response should be 30 minutes and uh five gigabytes, these are client facing, and then uh similar ones for the backend facing.
Recorded. Sorry this sat for two days without an answer.
The spec update, the folding unit of #6, adds size and time limits in both directions, between the client and the sidecar and between the sidecar and the app, for requests and responses alike. Each limit can be overridden by an environment variable.
Client-facing defaults are the values you gave: requests 60 seconds and 100 MB, responses 30 minutes and 5 GB.
Backend-facing defaults get similar values.
This also meets item 4 of #7: every limit has a stated default.
The repo is paused under the 2026-09-22 priority ruling. The unit runs when the repo resumes, and its PR closes this issue.
Model: opus-5-5
Recorded. Sorry this sat for two days without an answer.
The spec update, the folding unit of https://git.eeqj.de/sneak/smallwebwaf/issues/6, adds size and time limits in both directions, between the client and the sidecar and between the sidecar and the app, for requests and responses alike. Each limit can be overridden by an environment variable.
- Client-facing defaults are the values you gave: requests 60 seconds and 100 MB, responses 30 minutes and 5 GB.
- Backend-facing defaults get similar values.
This also meets item 4 of https://git.eeqj.de/sneak/smallwebwaf/issues/7: every limit has a stated default.
The repo is paused under the 2026-09-22 priority ruling. The unit runs when the repo resumes, and its PR closes this issue.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There need to be sane and defensive request size and time limits, and response size and time limits on both the client direction as well as the backend direction. The all of these values must be able to be overridden with environment variables, but the defaults should be same. I believe the same defaults for request should be 60 seconds and perhaps 100 megabytes. And the same defaults for response should be 30 minutes and uh five gigabytes, these are client facing, and then uh similar ones for the backend facing.
Recorded. Sorry this sat for two days without an answer.
The spec update, the folding unit of #6, adds size and time limits in both directions, between the client and the sidecar and between the sidecar and the app, for requests and responses alike. Each limit can be overridden by an environment variable.
This also meets item 4 of #7: every limit has a stated default.
The repo is paused under the 2026-09-22 priority ruling. The unit runs when the repo resumes, and its PR closes this issue.
Model: opus-5-5