Prepare for deprecation of FetchAPIRequest::request_context_type
This patch tries to make sure if not setting the given request_context_type for Fetch request doesn't break anything, before actually deprecating them. End state should be: * We remove FetchAPIRequest::request_context_type and URLRequest::fetch_request_context_type (if this doesn't break anything) * As a follow-up we can add the code to serialize/deserialize 'Request.destination' into CacheStorage, but it's not happening now (i.e. it's broken) More details: * Request's context type is not used when it's propagated to SW's fetch event or used for Cache Storage, and it seems it's WAI per spec (and request context type's not a spec'ed anymore) * Cache Storage's matching logic doesn't use them either. * Cache.keys() seem to be supposed to return the original request, therefore destination would need to be stored there, while the part's currently (already) broken Bug: 1045925 Change-Id: I4e95fe51b9a6b1d9f91226017e931f8a1d357a02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066359 Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#743442}
Showing
Please register or sign in to comment