Comment 12 for bug 1651923

The problem is: the http methods URL-encodes URLs before sending them, the https one does not. And our redirecting code decodes the locations given, because the http method encodes them.

This is of course horribly broken: We should not decode the location and re-encode it in the first place. That said, we can't fix this right now, so a simple work around for this issue is probably to just do the quoting in the https method as well.

I hope we can get rid of the https method, and just add TLS support to our own method - that will get rid of a lot of problems with the https one.