New issue
Advanced search Search tips

Issue 680574 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocking:
issue 679424



Sign in to add a comment

Implement the BlockOnce Integration Test with ChromeDriver

Project Member Reported by robertogden@chromium.org, Jan 12 2017

Issue description

Cc: robertogden@chromium.org
Labels: Integration-Test Pri-2 Type-Feature
Status: Available (was: Untriaged)

Comment 2 by bengr@chromium.org, Jan 23 2017

Owner: bengr@chromium.org
Status: Assigned (was: Available)
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 13 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3f40be110899bd6c3a4dc9a90daa10ba8adfe12c

commit 3f40be110899bd6c3a4dc9a90daa10ba8adfe12c
Author: bengr <bengr@chromium.org>
Date: Mon Feb 13 23:14:16 2017

Integration test of Data Saver block-once directive

The added test checks that a test HTML resource is not served
via the Data Saver proxy and that a subresource referenced in
the HTML is served via the proxy. The proxy is configured to
respond with the 'block-once' directive (a field of the
Chrome-Proxy header) if the test HTML resource is requested.

BUG= 680574 

Review-Url: https://codereview.chromium.org/2693873004
Cr-Commit-Position: refs/heads/master@{#450142}

[modify] https://crrev.com/3f40be110899bd6c3a4dc9a90daa10ba8adfe12c/tools/chrome_proxy/webdriver/bypass.py

Comment 4 by bengr@chromium.org, Feb 23 2017

Status: Fixed (was: Assigned)

Sign in to add a comment