forked from docs/doc-exports
Reviewed-by: Kovács, Zoltán <zkovacs@t-systems.com> Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com> Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
17 lines
1.2 KiB
HTML
17 lines
1.2 KiB
HTML
<a name="asm_faq_0008"></a><a name="asm_faq_0008"></a>
|
|
|
|
<h1 class="topictitle1">Why Does Not a Grayscale Policy that Based on Request Content Take Effect for Some Services?</h1>
|
|
<div id="body1546055873319"><div class="section" id="asm_faq_0008__section5424194519497"><h4 class="sectiontitle">Symptom</h4><p id="asm_faq_0008__p8597124618491">A grayscale policy that based on request content does not take effect on some services.</p>
|
|
</div>
|
|
<div class="section" id="asm_faq_0008__section1964105217499"><h4 class="sectiontitle">Analysis</h4><p id="asm_faq_0008__p3108954134910">A grayscale policy based on request content is valid only for the entry service that is directly accessed.</p>
|
|
</div>
|
|
<div class="section" id="asm_faq_0008__section10962275020"><h4 class="sectiontitle">Solution</h4><p id="asm_faq_0008__p82003312508">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. </p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="asm_faq_0006.html">Performing Grayscale Release</a></div>
|
|
</div>
|
|
</div>
|
|
|