New default request and byte limits, sized for one address shared by about 40 busy people (#161): requests 6000 a minute, 100,000 an hour and 1,000,000 a day; bytes 4 GiB a minute, 20 GiB an hour and 200 GiB a day; SWWAF_RESPONSE_MAX_BYTES 1 GiB, down from 5 GiB.
A health check test that no longer fails when another process takes a freed port (#158). Test code only.
To know before deploying: at the defaults, a response larger than 1 GiB, such as a clone of a large repository, is now cut off. Raising SWWAF_RESPONSE_MAX_BYTES, and the byte limits with it, lets it through.
Model: opus-5-5
What `next` has that `main` lacks:
- New default request and byte limits, sized for one address shared by about 40 busy people (https://git.eeqj.de/sneak/smallwebwaf/issues/161): requests 6000 a minute, 100,000 an hour and 1,000,000 a day; bytes 4 GiB a minute, 20 GiB an hour and 200 GiB a day; `SWWAF_RESPONSE_MAX_BYTES` 1 GiB, down from 5 GiB.
- A health check test that no longer fails when another process takes a freed port (https://git.eeqj.de/sneak/smallwebwaf/issues/158). Test code only.
To know before deploying: at the defaults, a response larger than 1 GiB, such as a clone of a large repository, is now cut off. Raising `SWWAF_RESPONSE_MAX_BYTES`, and the byte limits with it, lets it through.
Model: opus-5-5
The request limits and the hour and day byte limits now sit about twice
above what 40 people busy with heavy web apps make together on one
address:
- requests: 6000 a minute, 100,000 an hour, 1,000,000 a day;
- bytes: 20 GiB an hour, 200 GiB a day.
The largest response drops from 5 GiB to 1 GiB. The minute byte limit
of 4 GiB is sized to hold two of the largest responses with their
requests. SPEC.md gives the new reasoning; README.md and the reference
documents give the new figures.
Model: opus-5-5
TestHealthCheck closed the app's server, and later smallwebwaf, and
expected connections to the freed ports to fail. Another test could take
such a port in between, so the connection succeeded and the test failed.
The failing app check now uses the multicast address 224.0.0.1, to which
TCP cannot connect. The failing smallwebwaf check uses port 0, on which
nothing listens. Neither result depends on other processes. The test now
stops smallwebwaf after its last check, so that it exits before the
test's temporary directories are removed. The code under test is
unchanged.
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.
What
nexthas thatmainlacks:SWWAF_RESPONSE_MAX_BYTES1 GiB, down from 5 GiB.To know before deploying: at the defaults, a response larger than 1 GiB, such as a clone of a large repository, is now cut off. Raising
SWWAF_RESPONSE_MAX_BYTES, and the byte limits with it, lets it through.Model: opus-5-5
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.