我正在创建一个程序来删除CDN缓存。因此,我按照文档所说的那样做了,我仍然得到了这个:
{ "error":{ "code":"AuthenticationFailedInvalidHeader","message":“鉴权失败,提供的Authorization头部格式无效。”}}
因此,它基本上说明身份验证令牌本身格式错误(不是错误或过期)。尽管我按照文档建议的那样做了。
我的请求-响应流程如下所示(我混淆了真实数据):
REQUEST
POST /subscriptions/29bdq1a7-348b-48fe-b9e6-b90c432892ff/resourceGroups/cdn-4/providers/Microsoft.Cdn/Profiles/CDN-3-Premium/endpoints/custom-endpoint.azureedge.net/purge?api-version=2015-06-01 HTTP/1.1
Content-Length: 90
User-Agent: GuzzleHttp/6.1.1 curl/7.35.0 PHP/7.0.2-2+deb.sury.org~trusty+1
Host: management.azure.com
Authorization: SharedAccessSignature uid=56c6d48a66904d02ce030003&ex=2017-02-19T11:41:00.0000000Z&sn=9wBsmFuP1ps01rt8nVlvsiAIdJMOqNsmGaiXUlfT35RxOvWAjHHcSIQdJA8v9wGvX4bJgX5fu1QyqVG6y9iQ6Q==
Content-Type: application/json
{
"ContentPaths": [
"/uploads/static/ads_en.json",
"/pic2.jpg"
]
}
RESPONSE
HTTP/1.1 401 Unauthorized
Cache-Control: no-cache
Pragma: no-cache
Content-Type: application/json; charset=utf-8
Expires: -1
WWW-Authenticate: Bearer authorization_uri="https://login.windows.net/c87x6f33-af21-4461-a5b1-29647d8e9281", error="invalid_token", error_description="The authentication scheme of SharedAccessSignature is not supported."
x-ms-failure-cause: gateway
x-ms-request-id: 3514027b-e731-411c-b8es-cdf77d636284
x-ms-correlation-request-id: 3514137b-e731-411c-b8ee-cdf77d636284
x-ms-routing-request-id: WESTEUROPE:20160219T110919Z:3514037b-e731-411c-b7ee-cdf77d636184
Strict-Transport-Security: max-age=31536000; includeSubDomains
Date: Fri, 19 Feb 2016 11:09:19 GMT
Connection: close
Content-Length: 150
{"error":{"code":"AuthenticationFailedInvalidHeader","message":"Authentication failed. The 'Authorization' header is provided in an invalid format."}}\你能建议一下解决它的方法吗?
发布于 2016-03-08 02:41:21
我认为混淆的一部分是有两个截然不同的Azure管理API (与Azure API管理无关)。
有“服务管理”API和Azure资源管理器API (ARM)。
您正在使用的基本URL是用于ARM API的,并且它们不使用共享访问签名。关于直接调用ARM的最好的文章在这里,http://blog.davidebbo.com/2015/12/calling-arm-using-plain-rest.html
https://stackoverflow.com/questions/35504051
复制相似问题