Closed darkwing closed 8 years ago
We still see this in the Chrome console:
But IMO it's better than Firefox throwing a fetch error.
@marco-c @delapuente
With this PR, caching x-origin resources is lost. Or it is an intentional change (so in that case we should change the name of the method to something like normalize()
as we are anonymizing no more) or we must revert this change and simply delete referrer which is a more suitable specific solution.
@delapuente I think this PR hasn't modified the previous behavior for cross-origin requests. We're using the URL of the request to find an element in the cache, and if an element isn't found we're using fetch
with the original request.
From this line, I realized we don't reuse the url for fetching, only for cache matching. Then, there is no alteration in the semantics but I would recommend changing the name of the method to not lead to misconceptions #86.
This prevents the referrer problem as seen in issue #81 .