feat: add QUERY HTTP method support per RFC 10008#350
Conversation
Adds HttpMethod.QUERY to the HttpMethod enum so Azure Functions HTTP triggers can declare and handle the new QUERY method (RFC 10008), which provides a safe, read-only alternative to POST for requests requiring a body.
@microsoft-github-policy-service agree |
Adds two tests: one verifying HttpRequestConverter correctly passes through a QUERY request with a body, and one verifying HttpTrigger accepts HttpMethod.QUERY in its methods binding.
|
/azp run |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
The _test_http_external_app helper hardcoded the methods list for ASGI/WSGI catch-all routes. Since these routes register all HttpMethod enum members, adding QUERY to the enum caused the assertions to fail.
|
Hi @hallvictoria , it looks like I missed updating the ASGI/WSGI test assertions when adding the QUERY method. I've pushed a fix in the latest commit — the hardcoded methods list in _test_http_external_app now includes QUERY. All 765 tests pass locally. Could you re-trigger CI with /azp run? Please and thank you. |
|
/azp run |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
|
Hey @ajaymahadeven, thanks for this PR. Minor linting failures - can you please address? |
Hi @hallvictoria, apologies for that — fixed in the latest commit. All 767 tests pass locally including flake8. |
Adds HttpMethod.QUERY to the HttpMethod enum so Azure Functions HTTP triggers can declare and handle the new QUERY method (RFC 10008), which provides a safe, read-only alternative to POST for requests requiring a body.