Age | Commit message (Collapse) | Author |
|
The current quickstart document suggests to use pingora v0.1, but it
also suggests using the Opt::parse_args interface, which was introduced
in release v0.3.0. Update the quickstart document to suggest using v0.3
when setting up the cargo.toml file.
Addresses #432
Includes-commit: 9153a8a984d2e81304f8b7d6d338f1bfa126e5c3
Replicated-from: https://github.com/cloudflare/pingora/pull/433
|
|
Includes-commit: cd6f77726b2a5ca57f885af360de2ad0de788e87
Replicated-from: https://github.com/cloudflare/pingora/pull/402
Signed-off-by: spacewander <[email protected]>
|
|
Fix #363
---
updated
Includes-commit: 204ddb02743445e6204858b4df3ea3f28fa1911c
Includes-commit: 34c67f0acae52ce94a3a6d5696e0847e63b42be7
Replicated-from: https://github.com/cloudflare/pingora/pull/368
Signed-off-by: spacewander <[email protected]>
|
|
Don't unconditionally unwrap Sentry, guard it with a default value.
|
|
|
|
---
Update docs/user_guide/ratelimiter.md
---
docs: add upstream_request_filter to fix forbidden error of RateLimiter
---
Update ratelimiter.md
update rate_limiter_map initialize code
Co-authored-by: Dany Gagnon <[email protected]>
Co-authored-by: Xia Lei <[email protected]>
Includes-commit: 461d384966601a5fae60384cb0fef3fac9442218
Includes-commit: 80231711f9d85ee63a363c28a965acc86281b8df
Includes-commit: 99ed87f309b7d550b6a97af1c528a5849c020342
Includes-commit: bffc9f4f23c51feff64a1f6d3e9bfe8680e154d1
Replicated-from: https://github.com/cloudflare/pingora/pull/120
|
|
quickstart with no external dependencies
|
|
|
|
And other things.
Co-authored-by: DimanNe <[email protected]>
Co-authored-by: Xiaobo Liu <[email protected]>
Co-authored-by: houseme <[email protected]>
Co-authored-by: lilo <[email protected]>
Co-authored-by: Yang He <[email protected]>
|
|
Co-authored-by: Kevin Guthrie <[email protected]>
|
|
Co-authored-by: =?~~~?q?Ren=C3=A9=20Kla=C4=8Dan?= <[email protected]>
Co-authored-by: 12932 <[email protected]>
Co-authored-by: Alessandro <[email protected]>
Co-authored-by: InImpasse <[email protected]>
Co-authored-by: Paul James Cleary <[email protected]>
Co-authored-by: Yang Hau <[email protected]>
Co-authored-by: Morpheus <[email protected]>
Co-authored-by: mobeicanyue <[email protected]>
Co-authored-by: Twacqwq <[email protected]>
Co-authored-by: Bobby <[email protected]>
Co-authored-by: Dup4 <[email protected]>
Co-authored-by: Josh Soref <[email protected]>
Co-authored-by: Sheldon <[email protected]>
Co-authored-by: houseme <[email protected]>
Co-authored-by: ZhangIvan1 <[email protected]>
Co-authored-by: GrahamQuan <[email protected]>
Co-authored-by: =?~~~?q?Cristian=20Paul=20Pe=C3=B1aranda=20Rojas?= <[email protected]>
Co-authored-by: Nathan Sit <[email protected]>
Co-authored-by: David Lee <[email protected]>
Co-authored-by: Mengliang Su <[email protected]>
Co-authored-by: =?~~~?q?=EA=B9=80=EC=84=A0=EC=9A=B0?= <[email protected]>
Co-authored-by: Allen Huang <[email protected]>
Co-authored-by: Opacity <[email protected]>
Co-authored-by: cris <[email protected]>
Co-authored-by: Killian Ye <[email protected]>
Co-authored-by: Jiwei-dev <[email protected]>
Co-authored-by: Jinfeng Wang <[email protected]>
Co-authored-by: Ikko Eltociear Ashimine <[email protected]>
|
|
Previously only the response_filter would run on revalidated responses
with no way to process the upstream 304.
Also avoid passing through upstream 304 on revalidate
response_cache_filter errors and instead serve from cache. This
simplifies this edge case because it saves us from needing to check
whether the upstream header filter already ran on the 304 later.
|
|
Co-authored-by: Andrew Hauck <[email protected]>
Co-authored-by: Edward Wang <[email protected]>
|