Typo in section 3.1

[thw0rted]

Just before the 3.2 header there's a numbered list. Number 4, sub-item 3, reads in full as "Change the cache match algorithm to take". I think this sentiment was moved up to sub-item 1?

[letitz]

Partly, but I think some of the info is still missing. How exactly is the request network type populated? @mikewest for input on his original vision.

[letitz]

Response from Mike:

The core of the idea was to take the address space of the request into account when determining whether or not to accept a cached entry. That is, we should not use a cached response generated from https://a on a public network when evaluating requests to https://a loaded from a private network. This doesn't feel like a huge issue, but it's relatively straightforward-seeming to extend the cache entry with an address space, and to take that into account in the matching algorithms.