-
-
Notifications
You must be signed in to change notification settings - Fork 944
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
Proper HEAD
support for static routes
#2337
Comments
so, do we need to get the metadata only? |
Hello, |
Hi @Aanchallllll! However, as I understand, @akashverma0786 has also expressed interest, could you two coordinate so that we don't end up duplicating efforts? We have otherwise no shortage of issues 😅 |
Hi Anchal, Please go ahead with this issue, I will find myself another one, there are lots here . :) |
Cool beans, then it sounds like we have a plan. 😅 |
Hello, I would like to take this issue, where should I start? |
Hi @arthurprioli! We have otherwise no shortage of issues, we could find you another one 🙂 |
No problem! I'm looking for a refactoring like issue just to get me started. I'm using the "good first issues" label to check them out but I'd appreciate any recommendations for simpler issues to help me get started! |
I don't think we have good simple refactoring issues atm. |
Thanks for the suggestion! After taking a look I chose #1026 because it seemed more refactoration like, do you think it is a good idea? Thank you for your patience and time! |
Implement proper
HEAD
support for static file serving.The response should follow the same logic as the default
GET
behaviour (like now), but not open any file streams (because we do not need any as the response to aHEAD
request cannot have any body anyway).As a bonus, I think we need to block unsupported methods such as
POST
andPUT
, and render the correctAllow
header in response toOPTIONS
.The text was updated successfully, but these errors were encountered: