mox/http at f1259ee80e22d2b76be6d5d7fa5f22f5bfcc4373 - mox

mirror of https://github.com/mjl-/mox.git synced 2025-06-28 01:48:15 +03:00

History

Mechiel Lukkien f1259ee80e add config option to disable rate limiting for the webserver, and take a reverse proxy into account when finding the ip to use for webserver ratelimting

another approach i looked at was enabling/disabling rate limiting per
web handler. but we want to apply the rate limit as early as possible
(not after we've already done quite some work for the request), and with
per-handler rate limits on/off the code would be sprinkled with calls to
rate limiting. this is probably good enough for now. other protocols are
less likely to need this.

we were always using the ip address of the connection for rate limiting.
but some setups have a reverse proxy in front. if any handler on a
http/https port is marked as "forwarded" (with a reverse proxy), we use
the ip address from the x-forwarded-for header (like we already did for
authentication requests over http).

for issue #346

2025-05-15 20:16:49 +02:00

atime_bsd.go

make mox compile on windows, without "mox serve" but with working "mox localserve"

2023-10-14 10:54:07 +02:00

atime_windows.go

make mox compile on windows, without "mox serve" but with working "mox localserve"

2023-10-14 10:54:07 +02:00

atime.go

make mox compile on windows, without "mox serve" but with working "mox localserve"

2023-10-14 10:54:07 +02:00

autoconf_test.go

mox!