Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #11869

Closed (moved)
Open
Opened May 09, 2014 by Trac@tracbot

HTTPS Everywhere conflicts with other extensions like Tampermonkey

HTTPS Everywhere: 2014.4.25 for Chrome

Chrome: 34.0.1847.131 (Official Build 265687) for Windows

Problem:

It seems that what HTTPS Everywhere does is to "redirect" the address to the https attached one. But this doesn't work with some extensions.

For example, if a URL of a script in Tampermonkey matches a rule of HTTPS Everywhere, it will prevent the script from running normally.

My situation was that, I inserted a line of

// @require http://ajax.googleapis.com/ajax/libs/jquery/2.1.0/jquery.min.js

into my script, so that the script cannot fetch the js file normally.

Trac:
Username: Frederick888

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#11869