• Yutaka Hirano's avatar
    Update CORS error messages · fc0443b1
    Yutaka Hirano authored
    In preparation for out-of-blink CORS, this CL largely updates
    CORS error messages.
    
     1. "Failed to load" is removed from DocumentThreadableLoader, and
        "Access to..." is now used instead, in order to align with
        CORS error messages in ResourceLoader.
     2. We now use "Access to <type> at <last request url> (redirected
        from <initial request url>) from origin <origin> has been blocked
        by CORS policy:" for all CORS error messages. "(redirected from
        <initial request url>)" is omitted when <initial request url> and
        <last request url> are same.
     3. As implied at 2, "Redirect from <redirect src> to <redirect dest>
        has been blocked by CORS policy" is removed.
     4. Http status code is not shown any more.
     5. "Origin <origin> is therefore not allowed access." is redundant,
        so it is removed.
    
    Bug: 736308, 851419
    Change-Id: I1ceeab4a00a5cf4994acc317b792ffacd39db86d
    Reviewed-on: https://chromium-review.googlesource.com/1147890
    Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
    Reviewed-by: default avatarKinuko Yasuda <kinuko@chromium.org>
    Reviewed-by: default avatarAdam Rice <ricea@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#578221}
    fc0443b1
open-in-body-onload-sync-to-invalid-preflight-handling-expected.txt 3.13 KB