Skip to content

document that GET implies HEAD support #1885

Description

@joeyh

I understand that is a very common expectation for many web frameworks, but I still found it surprising that my servant server, which has a StreamGet endpoint for an internal API, also supported HEAD. In my case, HEAD unfortunately exposed a denial of service bug in my code, which I didn't think to test for because I didn't know it was supported.

Looking through the docs, I have not been able to find anywhere that documents that StreamGet or Get implies HEAD support. It's mostly documented by omission, since there's no explicit Head used in example API types, and indeed no Head verb. I suggest documenting it explicitly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions