So I am testing my application on a slow 3G network and I have noticed that Angular HTTP client takes it upon itself to cancel previous calls which is bad as I need all calls sent to the server (data and even header are different, just URL same). Again, the ID is diff, so it makes no sense for Angular to decide that it is ok to just cancel the previous call ... odd!
See attached image. I am NOT using switchMap so all calls are supposed to go through even in the slow 3G network but yet Angular HTTP client cancels previous calls.
this is my http call:
const httpOptions2 = {headers: new HttpHeaders({'Content-Type': 'application/json'}), responseType: 'text' as 'json', 'rand': Math.random()};
const url = `${this.coreAppData[0].webApiResellerBaseUrl}&command=UpdateUserPrivilege&privilegeId=${privilegeId}&accessMask=${accessMask}&customerUserName=${name}&rand=${Math.random()}`;
return this._http.get<any>(url, httpOptions2).pipe(
map((result: any) => result)
);
as you can see no switchMap and I even added a random arg for url and header to try and fix the issue with no success.
Here is what you can see in the network console.
How do you force HttpClient to send ALL commands to server and not drop previous calls EVEN if URL is same (which is my case args are diff so super odd)
Thanks,
Sean.