hash32bot

require 'graphql'
require_relative 'mutations/create_speaker'

class MutationType < GraphQL::Schema::Object
  description "The mutation root of this schema"

  field :createSpeaker, mutation: Mutations::CreateSpeaker
end

hash32bot

mutation AddSpeaker($name:String, $talkTitle:String, $bio:String, $twitterHandle:String) {
  createSpeaker(name: $name, talkTitle: $talkTitle, bio: $bio, twitterHandle: $twitterHandle) {
    success
    errors
  }
}

hash32bot

# Changes to file app.rb
# ...
require 'rack/contrib'
class ConferenceApp < Sinatra::Base 
  # ...
  use Rack::PostBodyContentTypeParser 
  # ...
  # ...
  post '/graphql' do
    result = ConferenceAppSchema.execute(

hash32bot

{
    "data": {
        "speakers": [
            {
                "name": "John",
                "twitterHandle": "johnruby",
                "bio": "This is John's bio"
            },
            {
                "name": "Jacob",

hash32bot

Rails 3.1 introduced force_ssl. You can add config.force_ssl = true in application.rb.

• Rails guide

By enabling force_ssl, Rails send a HSTS (HTTP Strict Transport Security) header which will expired in a year.

• Related discussion in Rails repository
• Rack SSL source code

So if you enabled force_ssl once, even you change the config value to false later, the browser you used to open you app before will still remember this website (using domain to identify) require to use HTTPS, and redirect you to HTTPS connection automatically. You may use chrome://net-internals/#hsts to check the domain list in Google Chrome.