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(307.2, 35%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFR%3C/text%3E%3C/svg%3E)
Good Morning,
We have multiple web applications running with the Azure application proxy. They are SPA applications (ReactJs) in which all calls are via Ajax.
Our problem occurs when a user has been connected for more than an hour. At that point, when making any Ajax call, they get a CORS error and the application is left in an inconsistent state.
When the user takes more than an hour, the proxy redirects him to login.microsoftonline.com / ... to check if his login is correct, but this check fails when we try to do it via Ajax. (see screenshot)
Is there any solution for this? Is there a way to avoid this redirect?
Thanks greetings.
Hi, we are looking into your issue and will update you accordingly!
Hi! I've checked with our escalation team. Please look over this document. If these suggestions don't fix your issue, please reply back and we will continue to investigate.
Best,
James
Good Morning,
The URL that you provide me I have already been looking at a few days ago.
The case that this tutorial exposes does not apply to me, it talks about CORS problems when you have two applications where one calls the other via AJAX.
My problem occurs when the Azure AD Application Proxy session expires. At that time all the requests are redirected to login.microsoftonline.com, I think that to start a new session. Those calls via AJAX do not work due to CORS problems.
I have searched about the subject but have not found any solution.
Thank you very much for your time, greetings.
The only solution we found was to increase the lifetime of the Azure proxy session, with that, until 12 hours the problem will not occur (and normally no user leaves the application open for so many hours).
Thank you.
The product group just got back to me with the same solution. So sorry we couldn't help you sooner, but I'm glad you figured it out!
Best,
James