FaceAPI使用申請で許可をいただき使用していたが、10月7日以降FaceAPIのリクエストが404エラーとなるが、解決策をしりたい

敬一吉田 25

FaceAPIの登録申請をし、許可をいただき、

2018年より使用していたFaceAPIでの顔認証を、継続利用していたが、10月7日より突然以下URLが404エラーとなり、使用不可の状態となっている

解決策をしりたい

https://westus.api.cognitive.microsoft.com/face/v1.0/detect?returnFaceId=true&returnFaceLandmarks=false

Updating the issue details AS-IS in English for the benefit of our Community audience.

I received permission in the FaceAPI application and used it, but since October 7th, FaceAPI requests have resulted in a 404 error.

I have been using facial recognition using FaceAPI since 2018, but from October 7th, the URL below suddenly became a 404 error and became unusable.

I want to know the solution

navba-MSFT 18,325 Reputation points Microsoft Employee

2023-10-13T06:51:00.4566667+00:00
@敬一吉田 Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

I understand that you have been using FaceAPI for facial recognition since 2018, but since October 7th, the URL you have been using has resulted in a 404 error. You are seeking a solution to this issue.

I hope that you have filled the Face Recognition intake form and got the access approved to use the face detection feature and API.

Please note, I was able to access the face detect api successfully for the WestUS endpoint and got 200 success code.

Action Plan:

Please try accessing from the Vision Studio and check if you see the same error.

Please invoke this REST API for Face Detect directly and update the right headers, key and request body as shown below and try:

Please confirm if you have used the right face attributes and the right detection model while invoking the face detect API.

Please check the response message (response body) while you received the 400 error code. The message field indicates the cause of the failure. see below:

{ "error": { "code": "BadArgument", "message": "XXXXXXX XXXXXXXX XXXX XXXXX XX XXXX" } }

If you still face the same issue after following the above action plan, please let me know. I would be happy to help.

On a side note: Starting June 30, 2023, existing customers will no longer be able to access facial recognition capabilities if their facial recognition application has not been approved. More Info here.

**
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
敬一吉田 25 Reputation points

2023-10-16T02:39:36.0633333+00:00
Thank you for your reply

If you run it using the facial recognition reception form, a 200 code will be returned to confirm that you are authenticated.

Even though the request URL is the same, the following exception occurs in "wresp = wr.GetResponse()" after executing the code "HttpWebRequest wr = (HttpWebRequest)WebRequest.Create(_url)".

{"Connection Lost: An unexpected error occurred while sending. ."}|System.Exception {System.Net.WebException}|

How can I retrieve data using "GetResponse()" as before?

RequestURL:
敬一吉田 25 Reputation points

2023-10-16T02:41:49.0566667+00:00

RequestURL:

https://westus.api.cognitive.microsoft.com/face/v1.0/detect?returnFaceId=true&returnFaceLandmarks=false&recognitionModel=recognition_04&returnRecognitionModel=false&detectionModel=detection_03&faceIdTimeToLive=86400

navba-MSFT 18,325 Microsoft Employee

@敬一吉田 Thanks for getting back. I used the below sample and it worked fine. You can try to test with the below sample after updating the Ocp-Apim-Subscription-Key.

Also note that you should be sending POST request and not a GET request.

using System;
using System.Net.Http;
using System.Threading.Tasks;
using System.Net.Http.Headers;

namespace FaceWebRequest
{
    internal class Program
    {
        static async Task Main(string[] args)
        {
            // Define the API endpoint URL
            string apiUrl = "https://westus.cognitiveservices.azure.com/face/v1.0/detect?returnFaceId=true&returnFaceLandmarks=false&returnFaceAttributes=headpose,mask,qualityforrecognition&recognitionModel=recognition_04&returnRecognitionModel=false&detectionModel=detection_03&faceIdTimeToLive=86400";

            // Create an HttpClient instance
            using (HttpClient client = new HttpClient())
            {
                // Set the base address of the API
                client.BaseAddress = new Uri(apiUrl);

                // Set the request headers
                client.DefaultRequestHeaders.Add("Ocp-Apim-Subscription-Key", "XXXXXXXXXX");
                client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));

                // Define the request body as a JSON string
                string jsonRequestBody = @"{
                ""url"": ""https://www.gravatar.com/avatar/205e460b479e2e5b48aec07710c08d50.jpg""
            }";

                // Create a StringContent from the JSON request body
                var content = new StringContent(jsonRequestBody, System.Text.Encoding.UTF8, "application/json");

                // Send the POST request
                HttpResponseMessage response = await client.PostAsync(apiUrl, content);

                // Check if the request was successful
                if (response.IsSuccessStatusCode)
                {
                    // Read and display the response content
                    string responseBody = await response.Content.ReadAsStringAsync();
                    Console.WriteLine("Response:");
                    Console.WriteLine(responseBody);
                }
                else
                {
                    Console.WriteLine("Request failed with status code: " + response.StatusCode);
                    // You can handle errors appropriately here
                }
            }
        }
    }
}

敬一吉田 25

Let me explain with the current source code.

This source code was working without any problems, but from October 7, 2023, the error I mentioned earlier started appearing in "GetResponse()".

I would like to know the reason why a program that used to have no problems started giving errors.

I feel like something has changed with FaceAPI, or it's something to do with the contract.

string[] detectAsync()
{
	string _url = "https://westus.api.cognitive.microsoft.com/face/v1.0/detect?returnFaceId=true&returnFaceLandmarks=false&recognitionModel=recognition_04&returnRecognitionModel=false&detectionModel=detection_03&faceIdTimeToLive=86400";
	string _key = this.subscriptionKey;
	HttpWebRequest wr = (HttpWebRequest)WebRequest.Create(_url);
	wr.ContentType = "application/octet-stream";
	wr.Method = "POST";
	wr.KeepAlive = true
	wr.Credentials = System.Net.CredentialCache.DefaultCredentials;
	wr.Headers.Add("Ocp-Apim-Subscription-Key", _key);
	Stream rs = wr.GetRequestStream();
	string responseStr = null;
	try
	{
		wresp = wr.GetResponse(); /*error here*/
		...
		...
}

navba-MSFT 18,325 Microsoft Employee

@敬一吉田 Thanks for getting back. I also tried with the above sample and it worked fine.

            string _url = "https://westus.cognitiveservices.azure.com/face/v1.0/detect?returnFaceId=true&returnFaceLandmarks=false&returnFaceAttributes=headpose,mask,qualityforrecognition&recognitionModel=recognition_04&returnRecognitionModel=false&detectionModel=detection_03&faceIdTimeToLive=86400";
            string _key = "XXXXXXXXXXXXXXXXXXXXXXX"; // Replace with your subscription key

            HttpWebRequest wr = (HttpWebRequest)WebRequest.Create(_url);
            wr.ContentType = "application/json";
            wr.Method = "POST";
            wr.Headers.Add("Ocp-Apim-Subscription-Key", _key);

            // Define the request body as a JSON string
            string jsonRequestBody = @"{
    ""url"": ""https://www.gravatar.com/avatar/205e460b479e2e5b48aec07710c08d50.jpg""
}";

            // Convert the JSON request body to a byte array
            byte[] postData = System.Text.Encoding.UTF8.GetBytes(jsonRequestBody);

            Stream rs = wr.GetRequestStream();
            rs.Write(postData, 0, postData.Length);
            rs.Close();

            HttpWebResponse wresp = (HttpWebResponse)wr.GetResponse();

            // Read and display the response content
            using (StreamReader streamReader = new StreamReader(wresp.GetResponseStream()))
            {
                string responseStr = streamReader.ReadToEnd();
                Console.WriteLine("Response:");
                Console.WriteLine(responseStr);
            }

            wresp.Close();

Action Plan: Our docs, doesn't mention about any changes being done to FACE API starting Oct 7th 2023.

Could you please share the complete response headers and response body that you received while getting 400 error code ? You can check this from fiddler trace while accessing your above code. This should help us identify the cause of the issue.

Awaiting your reply.

敬一吉田 25 Reputation points

2023-10-16T10:29:56.4266667+00:00
I ran the sample, but the same error occurred.

What I found out may be due to the deprecation of TLS 1.0/1.1.

I was able to avoid the error by adding the code below and enabling TLS 1.2.

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;

Accepted answer

navba-MSFT 18,325 Reputation points Microsoft Employee

2023-10-16T10:34:40.1666667+00:00

@敬一吉田 Thanks for the update. I'm glad to see you were able to resolve your issue.

Thanks for posting your solution so that others experiencing the same thing can easily reference this. Since the Microsoft Q&A community has a policy that the question author cannot accept their own answer, they can only accept answers by others, I'll repost your solution in case you'd like to Accept the answer.

Issue: You have been using FaceAPI for facial recognition since 2018, but since October 7th, the URL you have been using has resulted in a 404 error. You are seeking a solution to this issue.

Resolution:
You were able to resolve the issue by adding the below code and enabling TLS 1.2:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Share via

FaceAPI使用申請で許可をいただき使用していたが、10月7日以降FaceAPIのリクエストが404エラーとなるが、解決策をしりたい

0 additional answers