Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
H
HTTPS Everywhere Chrome
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 51
    • Issues 51
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • 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.

  • The Tor Project
  • Applications
  • HTTPS Everywhere Chrome
  • Issues
  • #8375

Closed
Open
Opened Mar 01, 2013 by cypherpunks@cypherpunks

HTTPS Everywhere for Chrome breaks redirects when authentication is required

I'm having a strange issue with HTTPS Everywhere.  It breaks server redirects over HTTPS on my site when authentication is also required.  It may also be related that I'm using a self-signed cert.

An example: https://nylen.tv/test should redirect to https://nylen.tv/test/ but it doesn't.  The server is sending the Location header properly, but Chrome does not follow it and shows the 301 page instead.   (The username for that URL is test and the password is testing).

What is even more strange is that if you refresh the page, the redirect happens like it's supposed to.

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: tpo/applications/https-everywhere-chrome#8375