Page MenuHomePhabricator

Add client-side check for protocol mismatch
ClosedPublic

Authored by asherkin on Jun 7 2016, 10:39 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jan 3, 2:25 PM
Unknown Object (File)
Tue, Dec 31, 10:48 PM
Unknown Object (File)
Wed, Dec 25, 9:49 PM
Unknown Object (File)
Sat, Dec 21, 3:21 AM
Unknown Object (File)
Sun, Dec 15, 12:23 AM
Unknown Object (File)
Dec 12 2024, 6:28 AM
Unknown Object (File)
Dec 11 2024, 10:29 PM
Unknown Object (File)
Dec 9 2024, 1:59 PM
Subscribers

Details

Summary

Fixes T10402.
I tried about 50 variations on the wording and notification layout, this seemed by far the most reasonable.
Didn't implement a way to ignore the warning, which might be required - but figured this is serious and broken enough while being completely invisible 99% of the time that it's worth shouting about.

Test Plan

Messed around with $_SERVER['HTTPS'] on the server side and client_uri on the client side - saw reasonable results in all combinations.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

asherkin retitled this revision from to Add client-side check for protocol mismatch.
asherkin updated this object.
asherkin edited the test plan for this revision. (Show Details)
epriestley added a reviewer: epriestley.

Cool, this looks great to me. Thanks!

One possible though is that we might want to send the user somewhere local and more narrowly tailored to the specific problem (in case we change preamble later, or that document gets bigger / less focused), but we can do that later if this proves confusing or whatever. There also isn't any particularly convenient way to ship the user somewhere reasonable right now without building a whole controller just for the one page.

This revision is now accepted and ready to land.Jun 7 2016, 1:35 PM
This revision was automatically updated to reflect the committed changes.