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
  • #5036

Closed (moved)
(moved)
Open
Created Feb 07, 2012 by Trac@tracbot

Google "sorry" captcha now supports HTTPS

Good news! It is now possible to do the Google captcha over HTTPS, but only through https://sorry.google.com/sorry/...

If you try instead https://www.google.com/sorry/... it will just redirect you to the Google homepage right away.

Another issue is that the "continue" GET variable, which holds the URL for redirection, will default to HTTP even if the original search was through HTTPS, so it will have to be rewritten, too.

I tried the following (rough) ruleset as a proof of concept, but for some reason it doesn't seem to do anything here (which may be a problem with my installation):

<ruleset name="GoogleSorry">
  <target host="www.google.com" />

  <rule from="^http://www\.google\.com/sorry/\?continue=http" to="https://sorry.google.com/sorry/\?continue=https" />
</ruleset>

Trac:
Username: ugh

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