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
Remove HeadResponder #3147
Remove HeadResponder #3147
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, @0xTim?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay in this. I think this is good, but I'd like to see a test for the explicit override of a HEAD request
8f88aad
to
23ecce2
Compare
@0xTim I think this is already covered by |
The HEAD method is identical to GET except that the server must not send content in the response (RFC 9110, section 9.3.2). The previous default behaviour of returning 200 OK to every HEAD request to a constant route is not standard-compliant. The new behaviour is to always forward the request to the GET route, unless the developer explicitly configured a custom HEAD route.
23ecce2
to
42658b5
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3147 +/- ##
==========================================
- Coverage 76.86% 76.54% -0.33%
==========================================
Files 211 211
Lines 8119 7677 -442
==========================================
- Hits 6241 5876 -365
+ Misses 1878 1801 -77
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I missed that. Ok this looks fine to me
@owainhunt since you did the original PR, does the overriding as described work for you?
LGTM 👍 |
* main: Patch configuration and log actual port on startup (vapor#3160) Update provider tests to 5.10 (vapor#3178) Migrate to Async NIOFileIO APIs (vapor#3167) Removed streamFile deprecation + deactivated advancedETagComparison by default (vapor#3177) Remove HeadResponder (vapor#3147) Advanced ETag Comparison now supported (vapor#3015) Enabled Request Decompression By Default (vapor#3175) HTTP2 Response Compression/Request Decompression (vapor#3126) Don't set ignore status for SIGTERM and SIGINT on Linux (vapor#3174) Fix typos across the codebase (vapor#3162) Fix some Sendable warnings on 5.10 (vapor#3158) Allow `HTTPServer`'s configuration to be dynamically updatable (vapor#3132) Fix issue when client disconnects midway through a stream (vapor#3102) Fix handling of "flag" URL query params (vapor#3151) Bump the dependencies group with 1 update (vapor#3148) Merge Async Tests (vapor#3141) Fix URI handling with multiple slashes and variable components. (vapor#3143) Fix broken URI behaviors (vapor#3140) # Conflicts: # Package.swift
These changes are now available in 4.93.1
The HEAD method is identical to GET except that the server must not send content in the response (RFC 9110, section 9.3.2).
The previous default behaviour of returning 200 OK to every HEAD request to a constant route is not standard-compliant.
The new behaviour is to always forward the request to the GET route, unless the developer explicitely configured a custom HEAD route.
This PR fixes #2680 and #2749.