fix: allow HEAD method for dynamic routes

[n-dusan]

Description (e.g. "Related to ...", etc.)

stelae is now able to resolve requests with HEAD method.

Code review checklist (for code reviewer to complete)

• Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
• Title summarizes what is changing
• Commit messages are meaningful (see this for details)
• Tests have been included and/or updated, as appropriate
• Docstrings have been included and/or updated, as appropriate
• Standalone docs have been updated accordingly

Automated tests, benchmarks and linters

You can run the tests, lints and benchmarks that are run on CI locally with:

just ci

[dgreisen]

question: does the response to a HEAD request return the full content? or does it just return the header info? It should be the latter, so shouldn't even need to get the blob out of the git repo, just know if it is there.

[n-dusan]

question: does the response to a HEAD request return the full content? or does it just return the header info?

A HEAD request returns just the header info. For example:

C:\Users\nikol>curl --head http://localhost:8080/cityofsanmateo/law-html/HEAD/metadata.json
HTTP/1.1 200 OK
content-length: 1324
content-type: application/json
date: Fri, 22 Nov 2024 17:07:32 GMT

shouldn't even need to get the blob out of the git repo, just know if it is there.

It seems that the blob is being read. Potentially because of the content-length header. So it runs the function to determine its response size.

From my understanding, this is how HEAD semantics typically work. But if you believe this behavior can or should be adjusted, please let me know!