The problem does not appear to have anything to do with SSL.  The
problem is that the chain of HTTP requests goes:

GET -> 302 -> 302 -> 301

On the final 301 urllib2's internal state is messed up such that by the
time its in the handle_error_302 method it believes the Location header
contains the following:

'http://www.wikispaces.com/\x00/?responseToken=481aec3249f429316459e01c00b7e522'

The \x00 and everything after it should not be there and is not there if
you look at what is sent over the socket itself.  The ?responseToken=xxx
value is leftover from the previous 302 response.  No idea where the
\x00 came from yet.  I'm debugging...