-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Cache] Unathorized clients should be blocked before accessing cache #899
Comments
vankoven
added a commit
that referenced
this issue
May 9, 2018
vankoven
added a commit
that referenced
this issue
May 9, 2018
vankoven
added a commit
that referenced
this issue
May 9, 2018
krizhanovsky
assigned aleksostapenko and vankoven and unassigned vankoven and aleksostapenko
Jul 15, 2018
vankoven
added a commit
that referenced
this issue
Sep 13, 2018
vankoven
added a commit
that referenced
this issue
Sep 24, 2018
vankoven
added a commit
that referenced
this issue
Dec 21, 2018
vankoven
added a commit
that referenced
this issue
Dec 22, 2018
vankoven
added a commit
that referenced
this issue
Jan 17, 2019
krizhanovsky
pushed a commit
that referenced
this issue
Jan 26, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a new request is received it's forwarded to cache first:
tempesta/tempesta_fw/http.c
Line 2373 in 195d85e
and only after that sticky cookie is checked:
tempesta/tempesta_fw/http.c
Lines 1966 to 1970 in 195d85e
That leads to unnecessary cache lookup for requests with violated or expired sticky cookie. Early blocking of unauthorized clients will help us to save resources under DDOS attacks.
The text was updated successfully, but these errors were encountered: