Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
Application Service Mesh
Application Service Mesh
- What's New
- Service Overview
- Getting Started
- User Guide
- Best Practices
-
FAQs
- Service Mesh Cluster
- Mesh Management
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Can't I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- Performing Grayscale Release
- Videos
On this page
Show all
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?
Why Does Not a Grayscale Policy that Based on Request Content Take Effect for Some Services?
Updated on 2023-07-03 GMT+08:00
Description
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
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
