Fix effective Origin URLs for IDB + Cache for file:/// pages

This is a terrible, horrible, no good, very bad hack.

Previously, storage APIs (notable, Indexed DB, Cache Storage) would
pass the origins they operated on from Blink to Chromium's
content/browser as a serialization done through
SecurityOrigin->DatabaseIdentifier->String->IPC->String->GURL. That
was simplified to SecurityOrigin->String->GURL->IPC. A side effect of
this was that pages browsed as file:// URLs would end up as invalid
GURLs due to stricter checks in the SecurityOrigin->String step.
Special case that conversion to restore the previous behavior.

R=michaeln@chromium.org,mkwst@chromium.org
BUG=595840

Review URL: https://codereview.chromium.org/1810193002

Cr-Commit-Position: refs/heads/master@{#382587}

0 files changed, 0 insertions, 0 deletions