Azure Function App Proxy到Blob存储帐户 [英] Azure Function App Proxy to a blob storage account

问题描述

使用新功能代理功能 ，我收到一个http 500错误，其代理配置如下:

Experimenting with the new function proxy feature, I get a http 500 error with a proxy configured as follows:

路由模板: /content/{*文件名}

Route template: /content/{*filename}

后端网址: https://my-storage-account.blob .core.windows.net/public/ {*文件名}

Backend URL: https://my-storage-account.blob.core.windows.net/public/{*filename}

后端只是Blob存储帐户上的公共容器.

Where the backend is just a public container on a blob storage account.

我尝试了带有和不带有文件扩展名的文件:favicon.ico和一个名为test的(文本)文件.

I've tried files with and without a file extension: favicon.ico and just a (text) file called test.

请求 https://my-function-app.azurewebsites.net/content/favicon.ico 产生404.

请求 https://my-function-app.azurewebsites.net/content/测试(不带扩展名"test"的文件)，会产生http 500错误.

Requesting https://my-function-app.azurewebsites.net/content/test (the file without an extension called "test"), yields a http 500 error.

我做错了什么?

注意::我使用host.json中的routePrefix选项删除了/api/前缀-这对我所有的功能都适用.加上/api/来请求上面的网址会为两个网址生成404.

Note: I have the /api/ prefix removed by using the routePrefix option in host.json - which works fine for all my functions. Requesting the urls above with the addition of /api/ yields a 404 for both urls.

推荐答案

现在已修复.应用服务团队提供了一个修复程序，并且工作正常.只需确保您使用的是代理运行时的最新版本(〜0.1)，然后将ROUTING_EXTENSION_VERSION从0.0.5升级到最新版本(当前为0.0.6)

It's fixed now. The App Service Team delivered a fix and it's working fine. Just make sure you are using the latest version of Proxy runtime(~0.1) and also upgrade the ROUTING_EXTENSION_VERSION from 0.0.5 to the latest version (currently 0.0.6)

更多信息: 查看全文