Skip to content
Browse files

Added text about utilizing thin for ssl.

  • Loading branch information...
1 parent 58c3125 commit 02256566312a5a524b748bb34a353e8b2d6b3929 @aantix committed
Showing with 15 additions and 5 deletions.
  1. +15 −5 README.rdoc
20 README.rdoc
@@ -50,6 +50,21 @@ Run the migrations :
rake db:migrate
+Mechanical Turk will open your forms in an iFrame from a secure URL (ssl).
+If you test locally with localhost, you're going to need to be running SSL so that you don't
+receive a mixed content warning within Chrome and a blank screen.
+Thin allows for local SSL.
+ # Gemfile
+ gem 'thin', :group => :development
+Then you can start the server by calling :
+ thin start --ssl
1) You should disable form controls if the Turker hasn't accepted the HIT. You can determine this from your controller:
@@ -185,11 +200,6 @@ option to designate a form url different from the default.
lifetime, duration, {}, {}, {:form_url => form_url})
-== Gotchas
-1) The application that hosts your external forms preferably should have an https interface (you're going to have to buy an SSL certificate). If the forms are hosted on an unsecured host (http), because Mechanical Turk defaults to https, you're going to receive the ugly popup from IE regarding "mixed content" (
== Copyright
Copyright (c) 2010 - 2012 Jim Jones. See LICENSE for details.

0 comments on commit 0225656

Please sign in to comment.
Something went wrong with that request. Please try again.