I have a simple authentication system in which I use UnityWebRequest objects to send a username and password and receive a registration token (which I store locally). On the server I have a .NET Core Web API and a MySQL database, which function as they should when I test them with Curl or Postman but not with Unity. Sometimes Unity receives a HTTP 200 response and a token when the server is down and sometimes Unity cannot find the server when it is up and running. My guess is that Unity caches the requests. Indeed, when I debug the server and send a request with Unity, it receives nothing. Adding a random number to my request does not fix it however. Adding "Cache-Control":"no-caching" to the header also does not change anything. I cannot find anything in the docs regarding caching of UnityWebRequest or cookies in Unity. Is there a way to turn it off or is there an alternative to using UnityWebRequest?