Open lf- opened 3 weeks ago
Is your feature request related to a problem? Please describe.
s3-proxy returns 405 errors for HEAD requests. This breaks various clients which want to determine the content type of a file or how large it is or similar information.
~ » curl --head https://install.lix.systems/install HTTP/2 405 server: nginx date: Sun, 18 Aug 2024 21:36:43 GMT allow: GET cache-control: no-cache, no-store, no-transform, must-revalidate, private, max-age=0 expires: Thu, 01 Jan 1970 00:00:00 GMT pragma: no-cache vary: Origin
I have inspected the config documentation here: https://oxyno-zeta.github.io/s3-proxy/configuration/structure/#actionsconfiguration and I do not think there is a way to enable it.
Describe the solution you'd like
Support HEAD requests per the HTTP spec.
Describe alternatives you've considered
There is not any real alternative to this, maybe a range of 0 to 0 or something but that is not entirely clear whether that works.
Additional context Add any other context or screenshots about the feature request here.
Hello @lf- ,
Sorry for being late on this.
I see the issue and I'm afraid that this isn't supported (yet). I will check how to do it. Thanks for the issue.
Oxyno-zeta
Is your feature request related to a problem? Please describe.
s3-proxy returns 405 errors for HEAD requests. This breaks various clients which want to determine the content type of a file or how large it is or similar information.
I have inspected the config documentation here: https://oxyno-zeta.github.io/s3-proxy/configuration/structure/#actionsconfiguration and I do not think there is a way to enable it.
Describe the solution you'd like
Support HEAD requests per the HTTP spec.
Describe alternatives you've considered
There is not any real alternative to this, maybe a range of 0 to 0 or something but that is not entirely clear whether that works.
Additional context Add any other context or screenshots about the feature request here.