Use kludge profiles based on user-agent #147
Labels
No Label
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#147
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Is your feature request related to a problem? Please describe.
S3 gateway contains a static list of kludges in config file to be compatible with certain clients. There are more kludges to come, see #146. While the list is static, admin should decide beforehand what kludges must be enabled.
Describe the solution you'd like
Use different approach to enable or disable the kludge: set on or off flags based on the user-agent for the request. Define list of kludges in the middleware and store kludge parameters in the context. Reuse it during request processing.
Describe alternatives you've considered
Keep kludges static in config.
Additional context
To do this, we should create some test suits for different application and libraries first, so we can test regression and add more kludges for different clients if needed.