-
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
Prohibit DELETE method in default configuration #2058
Labels
Milestone
Comments
krizhanovsky
added
low priority
good to start
Start form this tasks if you're new in Tempesta FW
labels
Feb 20, 2024
biathlon3
added a commit
to biathlon3/tempesta
that referenced
this issue
Mar 13, 2024
biathlon3
added a commit
to biathlon3/tempesta
that referenced
this issue
Mar 15, 2024
biathlon3
added a commit
to biathlon3/tempesta
that referenced
this issue
Apr 8, 2024
biathlon3
added a commit
to biathlon3/tempesta
that referenced
this issue
Apr 8, 2024
biathlon3
added a commit
to biathlon3/tempesta
that referenced
this issue
Apr 23, 2024
biathlon3
added a commit
to biathlon3/tempesta
that referenced
this issue
Apr 23, 2024
biathlon3
added a commit
to biathlon3/tempesta
that referenced
this issue
May 6, 2024
biathlon3
added a commit
to biathlon3/tempesta
that referenced
this issue
May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Scope
RFC defines DELETE as rm for resource that must invalidate the cache on successful response. However, Tempesta MUST NOT invalidate the cache on every DELETE request, it leads to uncontrolled invalidating of arbitrary resources. Therefore, need to prohibit DELETE method if it not explicitly allowed in configuration or prohibit cache invalidation using DELETE method.
The text was updated successfully, but these errors were encountered: