<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<blockquote type="cite">-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>FF 4.0b6 - nytimes.</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Sun, 24 Oct 2010 10:07:42 -0700</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>pat flaherty <a class="moz-txt-link-rfc2396E" href="mailto:patf@well.com"><patf@well.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:https-everywhere@eff.org">https-everywhere@eff.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Hi
Https-Everywhere is largely working with FF 4.0b6 - thanx.
One problem. When I follow links from <a class="moz-txt-link-freetext" href="https://www.nytimes.com">https://www.nytimes.com</a>, they
lead to blank pages. For one, the target url is http and not https
however I can't simply slip in the following 's' and have the link
work. I've deleted and recreated my FF profile several times which
might seem to help at first but it's quickly back to the same behavior.
secure.wikimedia.org and <a class="moz-txt-link-freetext" href="https://encrypted.google.com">https://encrypted.google.com</a> work fine in this
regard and so that might suggest the nytimes rules files.
How would I debug this? Or well short of that, how does one turn on
logging for the https-everywhere addon? I see log features in the code
but in spite of my fiddling around either I haven't turn it on correctly
or I'm not looking in the correct place for the messages.
pat
</pre>
</blockquote>
My nytimes link problem has gone away, at least for the moment.
I've recreated my profile now many times and I suspect that has
something to do with it.<br>
<br>
The following problem has been persistent. I've researched it some
and tracked it down to a fairly low level.<br>
<br>
I use google to find specific wikipedia topics - I find this works
better than Wikipedia's built-in search engine. I'd google say:<br>
<br>
wikipeida high performance computing<br>
<br>
and the wikipeida page I want would typically be the first link.
Except with https-everywhere on, clicking the target would again
(like nytimes previously) produce a blank page.<br>
<br>
What I found is that the incorrect behavior happens only when I'm
logged into google - when I'm not logged in the target page renders
properly. I find that the URLs in the 2 cases differ:<br>
<br>
Using FF 4's Web Console:<br>
<br>
<blockquote type="cite">SUCCESS<br>
Request URL:<br>
<a class="moz-txt-link-freetext" href="https://encrypted.google.com/url?sa=T&source=web&cd=1&ved=0CBQQFjAA&url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FHigh-performance_computing&ei=bVDUTOyiO5OasAOsvY2PCw">https://encrypted.google.com/url?sa=T&source=web&cd=1&ved=0CBQQFjAA&url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FHigh-performance_computing&ei=bVDUTOyiO5OasAOsvY2PCw</a><br>
<br>
Request Method:<br>
GET<br>
<br>
Status Code:<br>
HTTP/1.1 204 No Content<br>
<br>
<br>
Request URL:<br>
<a class="moz-txt-link-freetext" href="https://secure.wikimedia.org/wikipedia/en/wiki/High-performance_computing">https://secure.wikimedia.org/wikipedia/en/wiki/High-performance_computing</a><br>
<br>
Request Method:<br>
GET<br>
<br>
Status Code:<br>
HTTP/1.1 200 OK<br>
<br>
FAIL<br>
Request URL:<br>
<a class="moz-txt-link-freetext" href="https://encrypted.google.com/url?sa=t&source=web&cd=1&ved=0CBoQFjAA&url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FHigh-performance_computing&ei=l1DUTJs4haixA6PajI0L&usg=AFQjCNHGJdrIcFhxCdH_4EXE72GcnOJyoQ&sig2=zsHGXw4p8k-k0EUhWyqyzg">https://encrypted.google.com/url?sa=t&source=web&cd=1&ved=0CBoQFjAA&url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FHigh-performance_computing&ei=l1DUTJs4haixA6PajI0L&usg=AFQjCNHGJdrIcFhxCdH_4EXE72GcnOJyoQ&sig2=zsHGXw4p8k-k0EUhWyqyzg</a><br>
<br>
Request Method:<br>
GET<br>
<br>
Status Code:<br>
HTTP/1.1 302 Found<br>
<br>
Request URL:<br>
<a class="moz-txt-link-freetext" href="https://secure.wikimedia.org/wikipedia/en/wiki/High-performance_computing">https://secure.wikimedia.org/wikipedia/en/wiki/High-performance_computing</a><br>
<br>
Request Method:<br>
GET<br>
<br>
Status Code:<br>
HTTP/1.0 404 Not Found</blockquote>
<br>
Comparing the two URLs, I find that in the failed case (logged into
google) components, the payload of &ei= differs while &usg=
and &sgi2= are present in the failed case, but not the
successful.<br>
<br>
pat<br>
<br>
</body>
</html>