Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 4328: Proxying requests for sb-ssl.google.com for file proxy checks through sb-ssl.brave.com #2377

Merged
merged 2 commits into from
May 8, 2019

Conversation

jumde
Copy link
Contributor

@jumde jumde commented May 6, 2019

fix brave/brave-browser#4328

Submitter Checklist:

Test Plan:

  1. Start with a clean profile
  2. Wait for ~2 mins for SafeBrowsing store files to be downloaded in <DATA_DIR>/Safe Browsing
  3. Navigate to testsafebrowsing.appspot.com - Verify that the download checks work correctly
  4. Verify that no requests are sent to sb-ssl.google.com using a proxy (Fiddler for windows/linux and little snitch for mac-os)

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
  • Verify test plan is specified in PR before merging to source

After-merge Checklist:

  • The associated issue milestone is set to the smallest version that the
    changes has landed on.
  • All relevant documentation has been updated.

emerick
emerick previously approved these changes May 6, 2019
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I would also add a new unit test for this if possible.

@jumde jumde force-pushed the sbssl_proxy branch 2 times, most recently from 347a866 to e24dba0 Compare May 7, 2019 14:27
brave::ResponseCallback callback;
GURL::Replacements replacements;
replacements.SetHostStr(kBraveSafeBrowsingFileCheckProxy);
GURL expected_url(url.ReplaceComponents(replacements));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor: i think this test would be more precise if it tested for the literal expected string, like https://sb-ssl.brave.com/... instead of url.ReplaceComponents(replacements)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

Copy link
Member

@diracdeltas diracdeltas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm assuming tests pass. thanks for taking this

@emerick emerick self-requested a review May 8, 2019 13:06
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Proxy sb-ssl.google.com through sb-ssl.brave.com
4 participants