This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 83%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYA%3C/text%3E%3C/svg%3E)
When the b2c-signin screen is displayed, a request to add an XMLHttpRequest header and send a Json is executed. This POST method is probably a CSRF countermeasures.
The cache for this response is returned privately. Is there a way to control this, such as no cache?
/api/attachments/78006-b2csignin.png?platform=QnA
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 32%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJR%3C/text%3E%3C/svg%3E)
Thanks @YoshitakaAkimoto-3764. The B2C treats each policy as a separate authority. Thus the access tokens, refresh tokens and ID tokens returned from each policy are not interchangeable. So Could you please share the scenario to control the cache of b2C-signin?
Thanks @Jitendra Rai . I understand that it is incompatible with the response of other policies. My idea is not necessarily to control the cache. The response to this POST request doesn't include a header to invalidate the cache, but I'm wondering if it doesn't affect the cache because it doesn't include the body, I'm not sure.