-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
The built-in server responds to HEAD
requests with 404
#2851
Comments
I can add support for What are you using |
Yes, I see your point about the rebuild. It probably won't be required in most cases, but I guess it doesn't really hurt. My use case is as follow: I need to determine the URL of a file located next to the library file (it's some ancillary assets (fonts) that I need to load dynamically). In order to do that I need to resolve the URL of the library file, as in some cases (when using CDNs) the actual URL can be behind some redirects. Using a Those assets have been manually copied into the |
HEAD is also used purely for "is X still the latest?" requests via etag and/or content-length lookups (oof) Haven't had a moment to try out 0.17.x yet, but if there's still work being done in this space, it'd be great if |
Excellent! Thanks. |
I don't have a simple test case to share, however, the
ServeHTTP()
function inpkg/api/serve_other.go
file does indeed seem to only handleGET
(line 129). Instead it should probably handleHEAD
andGET
similarly, but avoid doing a rebuild or returning a body forHEAD
.The text was updated successfully, but these errors were encountered: