Microsoft Translator receiving error 405000, "The request method is not supported for the requested resource."

Question

Microsoft Translator receiving error 405000, "The request method is not supported for the requested resource."

Neale Faunt 26

I'm receiving this error using C# module that had previously been working for months. Using the following endpoint:

https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=en&to=zh-Hans" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'Hello, what is your name?'}]

Resource is global on paid Azure subscriptions. I regenerated the keys within Azure and inserted as the new key. Did something change that resulted in this not working?

svijay-MSFT 5,256 Reputation points Microsoft Employee Moderator

2021-05-10T12:04:54.647+00:00
Where is your code hosted. Is the machine using the code using TLS 1.2 ? All the cognitive services are enforced with TLS 1.2 and require TLS 1.2 to function.

The below is a simple Powershell script. Recommend you to test the below script on a different machine (a machine which has tls1.2 enabled - like windows 10 machine ) with your subscription key and see whether you are able to get the results.

$headers = @{"Ocp-Apim-Subscription-Key" = "<YOUR SUBSCRIPTION KEY>";"Content-Type"= "application/json";"charset"="UTF-8"} $response = Invoke-WebRequest -Uri "https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=en&to=zh-Hans" -Headers $headers -Body "[{'Text':'Hello, what is your name?'}]" -Method Post $response.Content
svijay-MSFT 5,256 Reputation points Microsoft Employee Moderator

2021-05-10T12:05:53.193+00:00

Also, when I was testing the behavior at my end, I was able to partially reproduce the issue at my end when the VERB was PUT (not POST). This may or may not be your case but wanted to highlight and it is safer to confirm the HTTP Verb (GET,PUT,POST etc) you are making use of.

Request :

**Response : **
Neale Faunt 26 Reputation points

2021-05-10T15:57:01.947+00:00

Hi Sathyamoorthy,

Thanks for getting back so quickly. Yes, I can confirm the Windows machine runs TLS 1.2. I've run the script and getting an error. The HTTP Verb used is "POST". I've included some screenshots showing script result, and my code.

Note, this code had run successfully for over a year prior to receiving the error sometime in April. No changes to my environment were made.

svijay-MSFT 5,256 Microsoft Employee Moderator

Strange. Can you pls run the below set of command in your machine. (If possible, can you run on a network in which there are less restriction ? )
This enforces to use TLS12

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$headers = @{"Ocp-Apim-Subscription-Key" = "<Your Subscription key>";"Content-Type"= "application/json";"charset"="UTF-8"}
$response = Invoke-WebRequest -Uri "https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=en&to=zh-Hans" -Headers $headers -Body "[{'Text':'Hello, what is your name?'}]" -Method Post

Neale Faunt 26 Reputation points

2021-05-11T15:34:22.927+00:00

Hello Sathyamoorthy;

You've drilled straight down to the issue. I have added the following line of code to the top of my function.

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

And everything works well now with no error.

You're the tops!

Neale

Accepted answer

0 additional answers

Your answer

svijay-MSFT 5,256 Reputation points Microsoft Employee Moderator

2021-05-10T12:04:54.647+00:00

Where is your code hosted. Is the machine using the code using TLS 1.2 ? All the cognitive services are enforced with TLS 1.2 and require TLS 1.2 to function.

The below is a simple Powershell script. Recommend you to test the below script on a different machine (a machine which has tls1.2 enabled - like windows 10 machine ) with your subscription key and see whether you are able to get the results.

$headers = @{"Ocp-Apim-Subscription-Key" = "<YOUR SUBSCRIPTION KEY>";"Content-Type"= "application/json";"charset"="UTF-8"} $response = Invoke-WebRequest -Uri "https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=en&to=zh-Hans" -Headers $headers -Body "[{'Text':'Hello, what is your name?'}]" -Method Post $response.Content
svijay-MSFT 5,256 Reputation points Microsoft Employee Moderator

2021-05-10T12:05:53.193+00:00

Also, when I was testing the behavior at my end, I was able to partially reproduce the issue at my end when the VERB was PUT (not POST). This may or may not be your case but wanted to highlight and it is safer to confirm the HTTP Verb (GET,PUT,POST etc) you are making use of.

Request :

**Response : **
Neale Faunt 26 Reputation points

2021-05-10T15:57:01.947+00:00

Hi Sathyamoorthy,

Thanks for getting back so quickly. Yes, I can confirm the Windows machine runs TLS 1.2. I've run the script and getting an error. The HTTP Verb used is "POST". I've included some screenshots showing script result, and my code.

Note, this code had run successfully for over a year prior to receiving the error sometime in April. No changes to my environment were made.
svijay-MSFT 5,256 Reputation points Microsoft Employee Moderator

2021-05-10T17:10:59.29+00:00

Strange. Can you pls run the below set of command in your machine. (If possible, can you run on a network in which there are less restriction ? )
This enforces to use TLS12

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 $headers = @{"Ocp-Apim-Subscription-Key" = "<Your Subscription key>";"Content-Type"= "application/json";"charset"="UTF-8"} $response = Invoke-WebRequest -Uri "https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=en&to=zh-Hans" -Headers $headers -Body "[{'Text':'Hello, what is your name?'}]" -Method Post
Neale Faunt 26 Reputation points

2021-05-11T15:34:22.927+00:00

Hello Sathyamoorthy;

You've drilled straight down to the issue. I have added the following line of code to the top of my function.

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

And everything works well now with no error.

You're the tops!

Neale

Answer 1

The powershell error looked more like a network error. So I had suggested running the below command :

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12  
 $headers = @{"Ocp-Apim-Subscription-Key" = "<Your Subscription key>";"Content-Type"= "application/json";"charset"="UTF-8"}  
 $response = Invoke-WebRequest -Uri "https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=en&to=zh-Hans" -Headers $headers -Body "[{'Text':'Hello, what is your name?'}]" -Method Post

The code [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 enforces to make use of the TLS 1.2. As mentioned in this article, Cognitive Services endpoints exposed over HTTP enforce TLS 1.2.

Translated code ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12; helped you to resolve your Issue.

----------------------

Please do not forget to "Accept the answer" wherever the information provided helps you. This will help others in the community as well.

Share via

Microsoft Translator receiving error 405000, "The request method is not supported for the requested resource."

0 additional answers

Your answer