Azure Search Basic中是否禁止OPTIONS请求? [英] Is OPTIONS request forbidden in Azure Search Basic?

查看:92
本文介绍了Azure Search Basic中是否禁止OPTIONS请求?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Azure Search Basic实例存在问题. tl; dr; 是来自浏览器的OPTIONS飞行前CORS请求在Search Basic中获得了403 FORBIDDEN.

We have an issue with Azure Search Basic instances. tl;dr; is that OPTIONS pre-flight CORS request from browser gets a 403 FORBIDDEN in Search Basic.

我们通过暂时转到Standard实例来解决此问题.

We resolved this by temporarily going to a Standard instance.

我们试图创建一个免费服务来测试和开发Angular网站的搜索服务,并且我们成功地做到了.当我们尝试上传整个数据集时,它超出了配额,因此我们切换到基本层.

We tried to create a Free service to test and develop a Search service for an Angular website, and we did so successfully. When we tried to upload the whole data set, it exceeded the quota, so we switched to a Basic tier.

我们更新了搜索的域和关键字,但由于它是跨域的,因此它在使用OPTIONS请求到达时开始回复403. CORS已正确配置,但我们甚至将其设置为允许所有来源,结果是相同的.

We updated the domain and key for the search, but it started to reply 403 when it was reached with the OPTIONS request, given that it is cross-domain. CORS was properly configured, but we even set it to allow all origins and the result was the same.

如果直接通过邮递员访问,则GET请求已正确解决.但是,OPTIONS返回了403.

If accessed directly via postman, the GET requests were correctly addressed. OPTIONS however returned 403.

我们正尝试修复问题,因此我们启动了Standard的一个实例,令我们惊讶的是它再次适用于整个数据集. 我们尝试在US EAST中进行测试时创建了三个Basic实例,所有这些实例都产生了相同的响应.

We were trying to hotfix an issue, so we spun up an instance of Standard and to our surprise it worked again with the whole data set. We created three Basic instances while trying to test this in US EAST and all of them resulted in the same response.

此功能是否由于预览而被禁用?

Is this disabled due to being preview?

推荐答案

这有望成功.这是一个错误,修复程序现已投入生产.对不起,麻烦了!

This is expected to work. It was a bug and the fix is now in production. Sorry for the trouble!

这篇关于Azure Search Basic中是否禁止OPTIONS请求?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆