Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • 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
  • #26548
Closed (moved) (moved)
Open
Created Jun 28, 2018 by cypherpunks@cypherpunks

Some HTTPS Everywhere functionality appears to be broken on 8.0a9

I compared the behavior between 8.0a8 and 8.0a9:

  • Open 8.0a8, and check the "Block all unencrypted requests" in the HTTPS-E popup.

  • Go to a mixedcontent website (go to the github repository efforg/https-everywhere then search for mixedcontent and find recent edited one, here's an example of such a site (not privatebin.net but the one written there): https://privatebin.net/?b5c69abb9501c2d5#fbNBF8M+XNeluv6+O00aGLjAWkrcUAnBDsgZLkP0RQY= )

  • So open that site up while your browser console is opened, you can see that HTTPS-E injects an upgrade-insecure-requests header and everything is going through HTTPS now including scripts and css etc.


  • Open 8.0a9, and check the "Block all unencrypted requests" in the HTTPS-E popup.

  • Go to the previously mentioned site.

  • There doesn't appear to be any injection of upgrade-insecure-requests header, css broken etc as a result.

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