Preserve referrer across CORS-enabled redirects

Preserve referrer across CORS-enabled redirects

When following a CORS-enabled redirect in DocumentThreadableLoader, use
the previous leg's referrer as the starting point instead of the
document's URL. This matches the Referrer Policy spec and ensures that
information is never added to the referrer when following a
redirect. (In other words, if the referrer is stripped in one leg of a
request, it will not be re-created in a subsequent leg.)

BUG=628457
Committed: https://crrev.com/8aa9abc54f9bfedcce035846a2cc898d5b252957
Cr-Commit-Position: refs/heads/master@{#406289}

[estark, 2016-07-18 19:29:11]

Description was changed from

==========
[DO NOT LAND] Preserve referrer across CORS-enabled redirects

When following a CORS-enabled redirect in DocumentThreadableLoader, use
the previous leg's referrer as the starting point instead of the
document's URL. This matches the Referrer Policy spec and ensures that
information is never added to the referrer when following a
redirect. (In other words, if the referrer is stripped in one leg of a
request, it will not be re-created in a subsequent leg.)

BUG=628457
==========

to

==========
Preserve referrer across CORS-enabled redirects

When following a CORS-enabled redirect in DocumentThreadableLoader, use
the previous leg's referrer as the starting point instead of the
document's URL. This matches the Referrer Policy spec and ensures that
information is never added to the referrer when following a
redirect. (In other words, if the referrer is stripped in one leg of a
request, it will not be re-created in a subsequent leg.)

BUG=628457
==========

[estark, 2016-07-18 22:11:23]

estark@chromium.org changed reviewers:
+ jochen@chromium.org

[estark, 2016-07-18 22:11:24]

jochen: WDYT? This makes it so that following a CORS redirect matches what the
net stack does when following redirects, what Firefox does, and what the spec
says to do.

[jochen (gone - plz use gerrit), 2016-07-19 12:21:45]

lgtm

[estark, 2016-07-19 15:55:09]

The CQ bit was checked by estark@chromium.org

[commit-bot: I haz the power, 2016-07-19 15:55:23]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-19 16:13:45]

Description was changed from

==========
Preserve referrer across CORS-enabled redirects

When following a CORS-enabled redirect in DocumentThreadableLoader, use
the previous leg's referrer as the starting point instead of the
document's URL. This matches the Referrer Policy spec and ensures that
information is never added to the referrer when following a
redirect. (In other words, if the referrer is stripped in one leg of a
request, it will not be re-created in a subsequent leg.)

BUG=628457
==========

to

==========
Preserve referrer across CORS-enabled redirects

When following a CORS-enabled redirect in DocumentThreadableLoader, use
the previous leg's referrer as the starting point instead of the
document's URL. This matches the Referrer Policy spec and ensures that
information is never added to the referrer when following a
redirect. (In other words, if the referrer is stripped in one leg of a
request, it will not be re-created in a subsequent leg.)

BUG=628457
==========

[commit-bot: I haz the power, 2016-07-19 16:13:46]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-07-19 16:13:49]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-19 16:16:46]

Description was changed from

==========
Preserve referrer across CORS-enabled redirects

When following a CORS-enabled redirect in DocumentThreadableLoader, use
the previous leg's referrer as the starting point instead of the
document's URL. This matches the Referrer Policy spec and ensures that
information is never added to the referrer when following a
redirect. (In other words, if the referrer is stripped in one leg of a
request, it will not be re-created in a subsequent leg.)

BUG=628457
==========

to

==========
Preserve referrer across CORS-enabled redirects

When following a CORS-enabled redirect in DocumentThreadableLoader, use
the previous leg's referrer as the starting point instead of the
document's URL. This matches the Referrer Policy spec and ensures that
information is never added to the referrer when following a
redirect. (In other words, if the referrer is stripped in one leg of a
request, it will not be re-created in a subsequent leg.)

BUG=628457

Committed: https://crrev.com/8aa9abc54f9bfedcce035846a2cc898d5b252957
Cr-Commit-Position: refs/heads/master@{#406289}
==========

[commit-bot: I haz the power, 2016-07-19 16:16:46]

Patchset 3 (id:??) landed as
https://crrev.com/8aa9abc54f9bfedcce035846a2cc898d5b252957
Cr-Commit-Position: refs/heads/master@{#406289}