New issue
Advanced search Search tips

Issue 893649 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 9
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 893647



Sign in to add a comment

Implement autoupgrade for mixed content websockets.

Project Member Reported by carlosil@chromium.org, Oct 9

Issue description

As part of the mixed content autoupgrade experiment, 'ws' websockets on https pages should be upgraded to 'wss' if the experiment is enabled.

 
Project Member

Comment 1 by bugdroid1@chromium.org, Oct 9

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

commit 515f9f20230ef2ca1921d8c8b746bafbbb27ddcd
Author: Carlos IL <carlosil@chromium.org>
Date: Tue Oct 09 18:05:15 2018

Added autoupgrade for mixed content websockets

Metrics will be added in a separate CL

Bug:893649

Change-Id: Ia3bb878675615a041f1648d05e09e56aafdfdfeb
Reviewed-on: https://chromium-review.googlesource.com/c/1270003
Commit-Queue: Carlos IL <carlosil@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#597990}
[modify] https://crrev.com/515f9f20230ef2ca1921d8c8b746bafbbb27ddcd/third_party/blink/renderer/modules/websockets/dom_websocket.cc
[modify] https://crrev.com/515f9f20230ef2ca1921d8c8b746bafbbb27ddcd/third_party/blink/renderer/modules/websockets/dom_websocket_test.cc

Status: Fixed (was: Started)

Sign in to add a comment