Opened 9 years ago

Closed 9 years ago

#5036 closed enhancement (fixed)

Google "sorry" captcha now supports HTTPS

Reported by: ugh Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Good news! It is now possible to do the Google captcha over HTTPS, but only through

If you try instead 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="" />

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

Child Tickets

Change History (5)

comment:1 Changed 9 years ago by ugh

Type: defectenhancement

comment:2 Changed 9 years ago by ugh

Here's a working and more comprehensive ruleset:

<ruleset name="GoogleSorry">
  <target host="" />
  <target host="" />
  <target host="" />

  <rule from="^https?://((sorry|www)\.)?google\.com/sorry/(Captcha)?\?continue=http([^s])" to="$4" />

comment:3 Changed 9 years ago by ugh

It just occured to me that the "continue" variable can in fact be ignored, and should be, because HTTPS Everywhere will properly take care of the subsequent request. So:

<ruleset name="GoogleSorry">
  <target host="" />
  <target host="" />
  <target host="" />

  <rule from="^http://((sorry|www)\.)?google\.com/sorry/" to="" />

comment:4 Changed 9 years ago by pde

comment:5 Changed 9 years ago by pde

Resolution: fixed
Status: newclosed

This has shipped in the development branch.

Note: See TracTickets for help on using tickets.