Taras Kushnir be96cf3d4c Refactor rate limiter out of auth middleware ...

Now we have a normalized sequence of "security" middlewares for public endpoints:
1. crash recovery (always first)
2. CDN security (whatever that means)
3. HTTP metrics (prometheus)
4. rate limiter (effect will be visible via metrics, but not logs)
5. out tracing (for logs)
6. All the rest

Since this commit, this sequence is same in both portal and API servers.

2025-07-08 17:56:40 +03:00

..

gc_test.go

Make siteverify API more resilient for unauthorized access

2025-06-21 14:16:28 +03:00

health_test.go

Improve monitoring

2025-06-08 13:27:37 +03:00

jobs_test.go

Fix extra transaction rollback error log

2025-06-17 09:23:17 +03:00

levels_test.go

Initial commit

2025-05-31 10:56:00 +03:00

middlewares.go

Refactor rate limiter out of auth middleware

2025-07-08 17:56:40 +03:00

puzzle_test.go

Update otter to v2

2025-06-17 20:35:18 +03:00

salt.go

Initial commit

2025-05-31 10:56:00 +03:00

server_test.go

Refactor rate limiter out of auth middleware

2025-07-08 17:56:40 +03:00

server.go

Refactor rate limiter out of auth middleware

2025-07-08 17:56:40 +03:00

verify_test.go

Reread cached properties from time to time

2025-06-21 14:16:28 +03:00