Help Center> Application Service Mesh> User Guide (ME-Abu Dhabi Region)> FAQs> Performing Grayscale Release> Why Does Not a Grayscale Policy that Based on Request Content Take Effect for Some Services?

Updated on 2024-03-15 GMT+08:00

View PDF

Why Does Not a Grayscale Policy that Based on Request Content Take Effect for Some Services?

Symptom

A grayscale policy that based on request content does not take effect on some services.

Analysis

A grayscale policy based on request content is valid only for the entry service that is directly accessed.

Solution

If you want a grayscale policy to be applied to all services in an application, the header information of the HTTP request needs to be transferred in the service code.

Parent topic: Performing Grayscale Release

Previous topic: Why Can't I Change the Image Used for the Grayscale Version When Performing Grayscale Release?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.