Fix a typo in ssl-forcing redirect

The ? is interepreted literally; requests for http://example.com are
redirected to https://example.com/?/ (which is fine, if ugly) but
requests for http://example.com/path are redirected to
https://example.com/?/path (which is definitely unworkable).

I have tested this change (in production, D: )