Skip to content

Conversation

@patrickhulce
Copy link
Collaborator

@patrickhulce patrickhulce commented Aug 23, 2021

Summary
Closes three holes in our isNonNetworkRequest logic:

  1. file protocol URLs were considered network requests.
  2. filesystem protocol URLs were considered network requests. (it's different!)
  3. When requests are blocked or otherwise don't receive a response the protocol field is left empty and requests weren't identified as non-network.

Related Issues/PRs
fixes #12915

@patrickhulce patrickhulce requested a review from a team as a code owner August 23, 2021 17:07
@patrickhulce patrickhulce requested review from adamraine and removed request for a team August 23, 2021 17:07
@google-cla google-cla bot added the cla: yes label Aug 23, 2021
@connorjclark
Copy link
Collaborator

connorjclark commented Aug 23, 2021

@patrickhulce
Copy link
Collaborator Author

patrickhulce commented Aug 23, 2021

@connorjclark in practice I was never able to observe filesystem actually be populated in these cases were you?

All file: URLs were blocked immediately in my tests which triggers the empty protocol branch. EDIT: filesystem is completely different from file got it 👍

We definitely have a larger issue lurking here with protocol and scheme being used interchangeably throughout the codebase even though they can be quite different (h2 vs. https). I'll file an issue for that 👍

@patrickhulce patrickhulce merged commit d982a31 into master Aug 23, 2021
@patrickhulce patrickhulce deleted the file_protocol_nonnetwork branch August 23, 2021 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Local Resources(file:///) highlighted as Render Blocking Resources

4 participants