How to use deactivate Webrick's SSL

Question

Last week I tried to debug with SSL activated in webbrick, but I forget how to restore the settings to default(without SSL). Every time I visit a controller, now it shows:

SSL connection error Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have. Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.

And below is the log from the console, can anyone help?

[2011-05-10 07:28:43] INFO WEBrick 1.3.1 [2011-05-10 07:28:43] INFO ruby 1.8.7 (2009-06-12) [universal-darwin10.0] [2011-05-10 07:28:43] INFO WEBrick::HTTPServer#start: pid=62854 port=3000 [2011-05-10 07:28:58] ERROR bad Request-Line `UQM?x?ʾ???????c??B?????n???BU???*???98?5EDf32?A/??'.

Answer 1

I had a similar issue but wasn't able to fix it by clearing cookies on Chrome (nor any other fixes like rake tmp:clear), and ended up switching to using thin with SSL enabled as suggested in this post:

https://stackoverflow.com/a/11614213

Added this to my Gemfile:

group :development do
   gem "thin"
end

Then bundle and thin start --ssl.

Answer 2

I had to use rake tmp:sessions:clear (not just rake:tmp:clear) as well as clearing cookies in the browser to fix this issue.

Answer 3

Similarly I recieved the same error after adding config.force_ssl = true in my config/locales/application.rb file

To remedy an SSL error, simply edit Rails.application.config.session_store :cookie_store, key: '_app_sessions' in config/initializers/session_store.rb

Changing the '_app_sessions' name to anything else will allow you to start your rails server without ssl and without error

Answer 4

I just ran into this same exact problem today. I added config.force_ssl = true to the application.rb file and got the above error. When I removed the line, the error still persisted.

I fixed it by clearing my browser cookies (Chrome in this case) and it works again. It seems the authentication information is saved in the cookie and something i that keeps reverting our requests to HTTPS but does not authenticate correctly so you get that error. Clearing the cookie solves that issue.