Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #8124

You need to sign in or sign up before continuing.
Closed (moved)
(moved)
Open
Created Jan 31, 2013 by Peter Eckersley@pde

[CHROME] implement downgrade rules and fix https -> https redirects

Per the EFF ruleset,

https://www.eff.org/sites/all/themes/frontier/images/get-https-e-chrome.png

should be rewritten to

https://www.eff.org/sites/all/themes/frontier/images/got-https-e-chrome.png

But in the chrome version of HTTPS Everywhere, it isn't.

We also haven't implemented the "downgrade" rule attribute that allows rewrites to http, where those are required (although arguably because chrome blocks mixed content, this is much less useful than it is in Firefox).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking