You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using http streams, the request.params object will be an empty object. The suggested workaround is to use a package like path-to-regexp to parse the request.url property. Keep in mind that Azure Functions only supports ASP.NET Core route templates (i.e. user/{name}) when registering your function, so you will likely need to use a different syntax (i.e. /user/:name) when parsing the url. Here is example code using the suggested workaround:
When using http streams, the
request.params
object will be an empty object. The suggested workaround is to use a package like path-to-regexp to parse therequest.url
property. Keep in mind that Azure Functions only supports ASP.NET Core route templates (i.e.user/{name}
) when registering your function, so you will likely need to use a different syntax (i.e./user/:name
) when parsing the url. Here is example code using the suggested workaround:Related to Azure/azure-functions-host#9840
The text was updated successfully, but these errors were encountered: