-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding HTTP method to ResourceTiming API structure #373
Labels
Comments
^^ @nicjansma |
Let's add this to the agenda for the WG for discussion this week |
Yes this seems very useful for being able to segment the performance of URLs that are used with different methods. REST APIs come to mind here. |
sohomdatta1
added a commit
to sohomdatta1/rt-explainer
that referenced
this issue
Apr 16, 2023
For posterity, we had discussed this on the April 13th, 2023 W3C WebPerf Working Group call. Summary:
|
Any updates on this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: