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(51.2, 34%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
My app has two parts: client and server. Both are web apps. They are connected through websocket. For some reason, if I first run the server in the browser (it shows just "upgrade required", which it is supposed to show), everything works just fine.
However, if I choose to run the client without first running the server in the browser, the server sends: "error 302".
The server has status running all the time.
On localhost everything works smoothly.
Please help
Hi, @Anatolii Kiguradze (Akvelon INC)
Does "Run in Browser" mean sending an HTTP request in a browser?
The simplest cause of general guidance that comes to mind is when the App Service Always On is disabled.
https://learn.microsoft.com/en-us/azure/app-service/configure-common?tabs=portal
By default, App Services will stop after being idle and will need to warm up the next time you connect.
If this doesn't help:
There may be other causes related to the session or service, but you need to know your client and server better.
Yes, sending an HTTP request manually in a browser
well, always on is on )). Still doesn't help.
Any suggestions maybe? At least to know in what direction to dig.
The issue was actually in authentication. The backend was trying to get user authentication behind the scenes and the client could not satisfy it obviously)