Hi,
Thank you for the work on this library , we largely depend on this library for our production-grade APIs.
While this may be bit too early , I was wondering if this is on the roadmap :
Support the new HTTP QUERY method defined in RFC 10008 for Azure Functions HTTP triggers.
Reference:
https://www.rfc-editor.org/info/rfc10008/
Background
The new HTTP QUERY method addresses the gap between GET and POST.
Currently, APIs often use:
GET for simple read operations where parameters are passed in the URL.
POST for complex read-only queries because it supports a request body.
However, using POST for read-only operations is not semantically ideal. The QUERY method provides a safe, read-only HTTP method that supports a request body for complex queries.
Proposed Feature
Allow Azure Functions HTTP triggers to handle QUERY requests in the same way they currently support methods such as:
- GET
- POST
- PUT
- PATCH
- DELETE
Example:
QUERY /api/products HTTP/1.1
Content-Type: application/json
{
"category": "laptops",
"brands": [
"Dell",
"Lenovo"
],
"price": {
"min": 1000,
"max": 2500
}
}
Hi,
Thank you for the work on this library , we largely depend on this library for our production-grade APIs.
While this may be bit too early , I was wondering if this is on the roadmap :
Support the new HTTP
QUERYmethod defined in RFC 10008 for Azure Functions HTTP triggers.Reference:
https://www.rfc-editor.org/info/rfc10008/
Background
The new HTTP
QUERYmethod addresses the gap betweenGETandPOST.Currently, APIs often use:
GETfor simple read operations where parameters are passed in the URL.POSTfor complex read-only queries because it supports a request body.However, using
POSTfor read-only operations is not semantically ideal. TheQUERYmethod provides a safe, read-only HTTP method that supports a request body for complex queries.Proposed Feature
Allow Azure Functions HTTP triggers to handle
QUERYrequests in the same way they currently support methods such as:Example: