Skip to content

Support HTTP Query Method #3730

Open
Open

Description

@DaddyWarbucks

The HTTP QUERY method was standardized in June 2026 under RFC 10008. This solves an interesting problem for Feathers. When using sockets, the query is serialized via JSON parse/stringify. But when using REST the query is transported via the URL, which leads to losing types (specifically around boolean and number).

For example
users?active=true will be parsed as { active: "true" } instead of { active: true }

Feathers v5 does have some nice query validation/coercion that help combat this. But I still think it would be nice to support QUERY.
I may whip up a little mixing that maps the QUERY method to the FIND method. But first class support seems achievable too.

Activity

  1. daffl commented on Nov 11, 2026

    @daffl
    Member

    I'm glad this finally went official! This would be great to have! I think it's pretty neat that - like with anything in HTTP - you can query with different content types. JSON is the obvious but you could also do things like

    QUERY /messages HTTP/1.1
    Host: example.org
    Content-Type: text/plain
    
    Give me all my messages talking about food
    

    Or upload an image or sound file to get a response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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