News for hackers. Stuff that matters.
Re:This is why sites choose to stay vulnerable to Firesheep by NiekvdMaas on Sunday November 07, 2010 @06:06PM (#1880634)
For Google Charts, there is a workaround. Simply change the hostname to www.google.com, example:

  http://chart.apis.google.com/chart?chs=200x200&cht=qr&chl=http://www.adperium.com/ (normal)
  https://www.google.com/chart?chs=200x200&cht=qr&chl=http://www.adperium.com/ (HTTPS)
It's probably not what Google prefers, but this works for us.
Re:This is why sites choose to stay vulnerable to Firesheep by jbyers on Sunday November 07, 2010 @06:26PM (#1880694)
It does work and Google definitely does not want the public to use it. A Googler's post on the topic from 2007:

http://groups.google.com/group/google-chart-api/msg/85186f74...

Re:This is why sites choose to stay vulnerable to Firesheep by nikcub on Sunday November 07, 2010 @06:29PM (#1880705)
In writing a plugin that rewrites URLs as https (http://github.com/nikcub/fidelio) I found that this worked in a lot of places. Facebook does not explicitly support ssl everywhere, but you can rewrite the requests to https servers and it works.