Closed GoogleCodeExporter closed 9 years ago
You can verify that it isn't a circularity in the server by opening a browser
and pasting in the URL. If the browser complains, it is a server issue and a
regression.
I found that the httpclient layer would handle the redirect to the https
connection, and then, if you tried later to communicate on the http:
connection, it would throw this exception. So you needed to remember whether
or not you needed to use https. I wasn't able to figure out how to
pro-actively discover whether you needed to use https or not.
Original comment by mitchellsundt@gmail.com
on 23 Jun 2011 at 12:10
Original comment by yanokwa
on 24 Jul 2011 at 3:36
Original comment by yanokwa
on 24 Jul 2011 at 3:48
Original issue reported on code.google.com by
yanokwa
on 22 Jun 2011 at 6:21Attachments: