Add service-workers race token to request and its lookup#1
Add service-workers race token to request and its lookup#1sisidovski wants to merge 2 commits intomainfrom
service-workers race token to request and its lookup#1Conversation
| <dt><var>request</var>'s <a for=request>service-workers race token</a> is not null | ||
| <dd> | ||
| <ol> | ||
| <li><p>Let <var>raceReesponse</var> to the result of [=lookup-race-response=] given <var>request</var>'s <a for=request>service-workers race token</a>, <var>request</var>'s <a for=request>reserved client</a>, <var>request</var>'s <a for=request>URL</a>. |
There was a problem hiding this comment.
Will [=lookup-race-response=] be defined in SW spec?
There was a problem hiding this comment.
Also, I guess we only do the matching for HTTP/HTTPS and GET request. Do we do such restriction here?
There was a problem hiding this comment.
Will [=lookup-race-response=] be defined in SW spec?
Yes. It's added in yoshisatoyanagisawa/ServiceWorker#10. I'm not sure if we have a good way to call an upcoming algorithm.
Also, I guess we only do the matching for HTTP/HTTPS and GET request. Do we do such restriction here?
Those are described in yoshisatoyanagisawa/ServiceWorker#10. The token is set under those restrictions. I guess we don't have to rephrase them.
|
This looks not a bikeshed code, I am not sure how external specifications can be linked here. |
yoshisatoyanagisawa
left a comment
yoshisatoyanagisawa
left a comment
There was a problem hiding this comment.
Then, I do not have any other comments.
|
Close this PR for now, and make another PR to the original fetch repository. |
|
Now the PR in whatwg#1737 |
2 participants
This is a fetch spec update corresponding to the change in yoshisatoyanagisawa/ServiceWorker#10