Azure-docs: GetQueryNameValuePairs does not exists in .Net Core

[7100SW]

For .Net Core, the
What is the equivalent of GetQueryNameValuePairs when using .Net Core 2.x?

// parse query parameter
string name = req.GetQueryNameValuePairs()
    .FirstOrDefault(q => string.Compare(q.Key, "name", true) == 0)
    .Value;

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ca056578-526c-603a-a0c7-fad5184134c0
• Version Independent ID: 486bd792-6be0-e4e4-8e81-c383591b4a87
• Content: Azure Functions HTTP triggers and bindings
• Content Source: articles/azure-functions/functions-bindings-http-webhook.md
• Service: azure-functions
• GitHub Login: @craigshoemaker
• Microsoft Alias: cshoe

[BryanTrach-MSFT]

@7100SW Thanks for the feedback! We are currently investigating and will update you shortly.

[PramodValavala-MSFT]

@7100SW Sorry about the outdated samples. We are in the process of updating the docs for Functions v2.

In the meantime, you can change req to type Microsoft.AspNetCore.Http.HttpRequest instead of System.Net.Http.HttpRequestMessage and get query params like this

string name = req.Query["name"];

We will keep this issue open for tracking the update of this specific doc.

[PramodValavala-MSFT]

@7100SW I hope my previous comment answers your query. To be thorough, here is a complete sample for V2

[FunctionName("MyHttpTrigger")]
public static async Task<IActionResult> Run(
    [HttpTrigger(AuthorizationLevel.Anonymous, "get", "post", Route = null)] HttpRequest req,
    ILogger log)
{
    log.LogInformation("C# HTTP trigger function processed a request.");

    string name = req.Query["name"];

    string requestBody = await new StreamReader(req.Body).ReadToEndAsync();
    dynamic data = JsonConvert.DeserializeObject(requestBody);
    name = name ?? data?.name;

    return name != null
        ? (ActionResult)new OkObjectResult($"Hello, {name}")
        : new BadRequestObjectResult("Please pass a name on the query string or in the request body");
}

We have assigned the issue to the content author to review and update the samples in this doc

[stimms]

One of the limiting factors with moving to HttpRequest is that it can't be used to generate the status responses from a durable function orchestration. This can be solved by using the compatability shim in Microsoft.AspNetCore.Mvc.WebApiCompatShim to get an HttpRequestMessage out of an HttpRequest

HttpRequestMessageFeature hreqmf = new HttpRequestMessageFeature(req.HttpContext);
HttpRequestMessage httpRequestMessage = hreqmf.HttpRequestMessage;
return starter.CreateCheckStatusResponse(httpRequestMessage, instanceId);

[craigshoemaker]

Thanks, again @7100SW for creating this issue.

We are still working toward a final fix, but for now I need to close this issue. Due to the volume of issues in our queue, our policy is to close issues that have been inactive for the last 90 days.

I will still update this thread once the final change is published to the remaining code samples.

Thanks again!

please-close