Intent to Prototype: HTTP method in ResourceTiming
Sohom Datta
Contact emails
datta...@gmail.comExplainer
https://github.com/sohomdatta1/rt-explainerSpecification
ResourceTiming PR: https://github.com/w3c/resource-timing/pull/375Summary
The ResourceTiming API structure doesn't currently give us insight into what HTTP method was used to fetch a specific resource and/or make an API call. As a part of this feature, a field will be added to the ResourceTiming structure that will allow developers to filter resources by the method used to fetch them.
Blink component
Blink>PerformanceAPIs>ResourceTimingMotivation
The addition of this field will allow for the following scenarios (per w3c/resource-timing#373): - Being able to debug and tease out specific cases where a POST request causes more overhead than a GET request and vice-versa. - Being able to segregate the performance of URLs based of the HTTP methods used to access them (for example when monitoring a REST API)
Initial public proposal
https://github.com/w3c/resource-timing/issues/373TAG review
NoneTAG review status
PendingRisks
Interoperability and Compatibility
None
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Debuggability
None
Is this feature fully tested by web-platform-tests?
None yet, but WPT tests will be written alongside implementationFlag name
None, expected to be "PerformanceResourceTimingHttpMethod"Finch feature name
NoneNon-finch justification
NoneRequires code in //chrome?
FalseTracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1433676Estimated milestones
No milestones specified