You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ResourceTiming API structure doesn't currently give us insight into what HTTP method was used to fetch a specific resource and/or make a API call. It would be great if the HTTP method used to make a specific HTTP request could be added to the ResourceTiming structure.
The major usecase where I see this getting used (and from where this idea came from) is to debug cases where a POST request would have additional latency/overhead over a GET request or vice-versa.