Sorry to revive a month old thread; this discussion is coming up again
on the web.py list here:
http://groups.google.com/group/webpy/browse_thread/thread/1755ffad8f2b4d2a
Basically, while its true that the error indicates that the client
made an HTTP request to an HTTPS server, the correct action would be
to return 400 Bad Request. In debugging this problem, I noticed that
cherrypy is actually trying to send this correct response when the
given exception is thrown. Apparently, It identifies an HTTP request,
tries to respond that it only accepts HTTPS, but when it responds it
tries to speak HTTPS when it shouldn't be. Any advice would be
appreciated.
Thanks,
Dusty