Help Center>
Application Service Mesh>
FAQs>
Performing Grayscale Release>
Why Does Not a Grayscale Policy that Based on Request Content Take Effect for Some Services?
Updated on 2024-01-24 GMT+08:00
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
Performing Grayscale Release FAQs
- Why Can't I Change the Image Used for the Grayscale Version When Performing Grayscale Release?
- Why Does Not a Grayscale Policy that Based on Request Content Take Effect for Some Services?
- InvalidRequestBody Is Reported When a Grayscale Release Task Is Created for a Service with Multiple Ports
Feedback
Was this page helpful?
Provide feedbackThank 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.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
