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(112.00000000000001, 81%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
We have 2 sites deployed in same server authenticated via Azure. While accessing one site it shows cookie highlighted in the screenshot with past date expiry whereas the second site shows as expected which is shown in second image.
Due to this all async calls are failing and every page refresh causes redirect to login.microsoftonline.com and again creating same expired cookie.
Can someone please point out what would be difference in setting which is causing this?
This happens in Chrome and Edge browser only but both sites work in IE. Also it doesn't happen for all users.
Hello @Raj , I'm reaching within the product team and will come back to you.
Thank you anonymous user-msft Users are forced to use IE due to this issue.
Hi, do you still require assistance?
Thank you,
James
This ended up being a file permission issue within the application that IIS wasn't able to serve.
Only odd thing about the issue was Azure app proxy cookie not being set due to this making us to think it was related to Azure app setting.
Hi @Raj . Please collect a Fiddler log or a HAR file using chrome developer tools for both the working and not-working scenario (whole flow) and create a support request to later attach such information.
Sure anonymous user-msft Let me get the details from user machine and will create Support Request.
Hi anonymous user-msft
Looks like it would take more than a day to get logs as they need to confirm if such trace can be shared outside of company.
From the behavior shown in screenshots, can you suggest based on previous encounters if there are any settings that we need to check in Azure with respect to non-working application and why it would set expiry to a past date?
Thanks!
Hi @Raj , not really. This might end being reviewed by the product team which will require the requested information.