尝试在southasia中使用Translator Text API v3.0 [英] Trying to use the Translator Text API v3.0 in southasia
问题描述
使用https://github.com/MicrosoftTranslator/Text-Translation-API-V3-NodeJS/blob/master/Translate.js中的翻译示例代码
我在Southasia有一个资源,但是当我尝试连接时,我得到一个404:资源未找到 ??????? b b p
我应该使用什么端点:
1) https://api.cognitive.microsofttranslator.com/
2)https://southeastasia.api.cognitive.microsoft.com/
那么正确的URL是什么?
问候
Terence
我认为你应该使用以下内容:
< table style ="font-family:'Segoe UI',SegoeUI,'Segoe WP','Helvetica Neue',Helvetica,Tahoma,Arial,sans-serif; border-collapse:collapse; border-spacing:0px; table-layout :auto; width:654px; font-size:0.875rem">
的 API- apc.cognitive.microsofttranslator.com
请参考以下内容:
Microsoft Translator在多个数据中心位置提供服务。目前它们位于6 Azure
区域 :
美洲: 美国西部2和美国中西部- 亚太地区: 东南亚和韩国南部
- 欧洲: 北欧和西欧
Microsoft转换器Text API的请求在大多数情况下由最接近请求发起地的数据中心处理。如果数据中心发生故障,请求可能会被路由到区域。
要强制请求由特定数据中心处理,请将API请求中的全局端点更改为所需的区域端点:
描述
Region
基本网址
< tbody style ="">
Azure
全球
api.cognitive.microsofttranslator.com
Azure
北美
api-nam.cognitive.microsofttranslator.com
Azure
欧洲
api-eur.cognitive.microsofttranslator.com
Azure
亚太地区
api-apc.cognitive.microsofttranslator.com
Used the translator example code in https://github.com/MicrosoftTranslator/Text-Translation-API-V3-NodeJS/blob/master/Translate.js
I have a resource in Southasia, but when I try to connect I get a 404: Resource not found ???
What endpoint should I use:
1) https://api.cognitive.microsofttranslator.com/
2) https://southeastasia.api.cognitive.microsoft.com/
And then what is the correct URL?
Regards
Terence
解决方案Hi,
I think you should use the following:
api-apc.cognitive.microsofttranslator.com
Please also refer to following:
Microsoft Translator is served out of multiple datacenter locations. Currently they are located in 6 Azure regions:
Americas: West US 2 and West Central US- Asia Pacific: Southeast Asia and Korea South
- Europe: North Europe and West Europe
Requests to the Microsoft Translator Text API are in most cases handled by the datacenter that is closest to where the request originated. In case of a datacenter failure, the request may be routed outside of the region.
To force the request to be handled by a specific datacenter, change the Global endpoint in the API request to the desired regional endpoint:
Description Region Base URL Azure Global api.cognitive.microsofttranslator.com Azure North America api-nam.cognitive.microsofttranslator.com Azure Europe api-eur.cognitive.microsofttranslator.com Azure Asia Pacific api-apc.cognitive.microsofttranslator.com
这篇关于尝试在southasia中使用Translator Text API v3.0的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文