Use https:// everywhere where possible

Replace any existing http:// URLs with https:// where supported.

graphql.gemspec

@@ -10,7 +10,7 @@ Gem::Specification.new do |s|
   s.date        = Date.today.to_s
   s.summary     = "A GraphQL language and runtime for Ruby"
   s.description = "A plain-Ruby implementation of GraphQL."
-  s.homepage    = "http://github.com/rmosolgo/graphql-ruby"
+  s.homepage    = "https://github.com/rmosolgo/graphql-ruby"
   s.authors     = ["Robert Mosolgo"]
   s.email       = ["rdmosolgo@gmail.com"]
   s.license     = "MIT"

guides/_config.yml

@@ -1,6 +1,6 @@
 title: GraphQL Ruby
 baseurl: ""
-url: "http://graphql-ruby.org"
+url: "https://graphql-ruby.org"
 
 exclude:
   - .gitignore

guides/_layouts/default.html

@@ -24,7 +24,7 @@
           <a href="{% api_doc_root %}">API</a>
           <a href="https://tinyletter.com/graphql-ruby">Newsletter</a>
           <a href="https://github.com/rmosolgo/graphql-ruby">Source Code</a>
-          <a href="http://graphql.pro">Upgrade to Pro</a>
+          <a href="https://graphql.pro">Upgrade to Pro</a>
           <input
             class="search-input"
             onkeyup="GraphQLRubySearch.run(this)"

guides/_layouts/guide.html

@@ -34,7 +34,7 @@
     <p>
       <strong>⚡️ Pro Feature ⚡️</strong>
       <span style="font-style: italic;">
-        This feature is bundled with <a href="http://graphql.pro">GraphQL-Pro</a>.
+        This feature is bundled with <a href="https://graphql.pro">GraphQL-Pro</a>.
       </span>
     </p>
   </div>

guides/_sass/reset.scss

@@ -1,4 +1,4 @@
-/* http://meyerweb.com/eric/tools/css/reset/
+/* https://meyerweb.com/eric/tools/css/reset/
    v2.0 | 20110126
    License: none (public domain)
 */

guides/authorization/can_can_integration.md

@@ -9,7 +9,7 @@ pro: true
 ---
 
 
-[GraphQL::Pro](http://graphql.pro) includes an integration for powering GraphQL authorization with [CanCan](https://github.com/CanCanCommunity/cancancan).
+[GraphQL::Pro](https://graphql.pro) includes an integration for powering GraphQL authorization with [CanCan](https://github.com/CanCanCommunity/cancancan).
 
 __Why bother?__ You _could_ put your authorization code in your GraphQL types themselves, but writing a separate authorization layer gives you a few advantages:
 

guides/authorization/overview.md

@@ -135,4 +135,4 @@ To accomplish these, you can use GraphQL-Ruby's authorization framework. The fra
 - {% internal_link "Accessibility", "/authorization/accessibility" %} prevents running queries which access parts of the GraphQL schema, unless users have the required permission.
 - {% internal_link "Authorization", "/authorization/authorization" %} checks application objects during execution to be sure the user has permission to access them.
 
-Also, [GraphQL::Pro](http://graphql.pro) has integrations for {% internal_link "CanCan", "/authorization/can_can_integration" %} and {% internal_link "Pundit", "/authorization/pundit_integration" %}.
+Also, [GraphQL::Pro](https://graphql.pro) has integrations for {% internal_link "CanCan", "/authorization/can_can_integration" %} and {% internal_link "Pundit", "/authorization/pundit_integration" %}.

guides/authorization/pundit_integration.md

@@ -8,7 +8,7 @@ index: 4
 pro: true
 ---
 
-[GraphQL::Pro](http://graphql.pro) includes an integration for powering GraphQL authorization with [Pundit](https://github.com/varvet/pundit) policies.
+[GraphQL::Pro](https://graphql.pro) includes an integration for powering GraphQL authorization with [Pundit](https://github.com/varvet/pundit) policies.
 
 __Why bother?__ You _could_ put your authorization code in your GraphQL types themselves, but writing a separate authorization layer gives you a few advantages:
 

guides/development.md

@@ -27,7 +27,7 @@ Then, install the dependencies:
 
 - Install SQLite3 and MongoDB (eg, `brew install sqlite && brew install mongodb`)
 - `bundle install`
-- Optional: [Ragel](http://www.colm.net/open-source/ragel/) is required to build the lexer
+- Optional: [Ragel](https://www.colm.net/open-source/ragel/) is required to build the lexer
 
 ### Running the Tests
 
@@ -121,7 +121,7 @@ BUNDLE_GEMFILE=gemfiles/rails_5.gemfile bundle exec rake
 
 ### Debugging with Pry
 
-[`pry`](http://pryrepl.org/) is included with GraphQL-Ruby's development setup to help with debugging.
+[`pry`](https://pryrepl.org/) is included with GraphQL-Ruby's development setup to help with debugging.
 
 To pause execution in Ruby code, add:
 
@@ -224,7 +224,7 @@ Then, check them out locally:
 
 ```
 $ bundle exec rake site:serve
-# then visit localhost:4000/api-doc/1.8.0/
+# then visit http://localhost:4000/api-doc/1.8.0/
 ```
 
 Then, publish them as part of the whole site:

guides/errors/execution_errors.md

@@ -8,7 +8,7 @@ desc: The top-level "errors" array and how to use it.
 index: 1
 ---
 
-The GraphQL specification [allows for a top-level `"errors"` key](http://facebook.github.io/graphql/October2016/#sec-Errors) in the response which may contain information about what went wrong during execution. For example:
+The GraphQL specification [allows for a top-level `"errors"` key](https://facebook.github.io/graphql/October2016/#sec-Errors) in the response which may contain information about what went wrong during execution. For example:
 
 ```ruby
 {
@@ -62,7 +62,7 @@ When this error is raised, its `message` will be added to the `"errors"` key and
 
 ## Customizing Error JSON
 
-The default error JSON includes `"message"`, `"locations"` and `"path"`. The [forthcoming version](http://facebook.github.io/graphql/draft/#example-fce18) of the GraphQL spec recommends putting custom data in the `"extensions"` key of the error JSON.
+The default error JSON includes `"message"`, `"locations"` and `"path"`. The [forthcoming version](https://facebook.github.io/graphql/draft/#example-fce18) of the GraphQL spec recommends putting custom data in the `"extensions"` key of the error JSON.
 
 You can customize this in two ways:
 

guides/getting_started.md

@@ -41,7 +41,7 @@ Or, you can build a GraphQL server by hand:
 
 ### Declare types
 
-Types describe objects in your application and form the basis for [GraphQL's type system](http://graphql.org/learn/schema/#type-system).
+Types describe objects in your application and form the basis for [GraphQL's type system](https://graphql.org/learn/schema/#type-system).
 
 ```ruby
 # app/graphql/types/post_type.rb
@@ -66,7 +66,7 @@ end
 
 ### Build a Schema
 
-Before building a schema, you have to define an [entry point to your system, the "query root"](http://graphql.org/learn/schema/#the-query-and-mutation-types):
+Before building a schema, you have to define an [entry point to your system, the "query root"](https://graphql.org/learn/schema/#the-query-and-mutation-types):
 
 ```ruby
 class QueryType < GraphQL::Schema::Object
@@ -124,14 +124,14 @@ See {% internal_link "Executing Queries","/queries/executing_queries" %} for mor
 
 ## Use with Relay
 
-If you're building a backend for [Relay](http://facebook.github.io/relay/), you'll need:
+If you're building a backend for [Relay](https://facebook.github.io/relay/), you'll need:
 
 - A JSON dump of the schema, which you can get by sending [`GraphQL::Introspection::INTROSPECTION_QUERY`](https://github.com/rmosolgo/graphql-ruby/blob/master/lib/graphql/introspection/introspection_query.rb)
 - Relay-specific helpers for GraphQL, see the `GraphQL::Relay` guides.
 
 ## Use with Apollo Client
 
-[Apollo Client](http://dev.apollodata.com/) is a full featured, simple to use GraphQL client with convenient integrations for popular view layers. You don't need to do anything special to connect Apollo Client to a `graphql-ruby` server.
+[Apollo Client](https://www.apollographql.com/) is a full featured, simple to use GraphQL client with convenient integrations for popular view layers. You don't need to do anything special to connect Apollo Client to a `graphql-ruby` server.
 
 ## Use with GraphQL.js Client
 

guides/index.html

@@ -20,7 +20,7 @@ <h2>Install the Gem</h2>
       <div class="teaser">
         <p>
           <a href="{{ site.baseurl}}/getting_started">Get going fast</a> with the <code><a href="https://rubygems.org/gems/graphql">graphql</a></code> gem,
-          battle-tested and trusted by <a href="https://githubengineering.com/the-github-graphql-api/#open-source">GitHub</a>, <a href="http://www.graphql.com/articles/graphql-at-shopify">Shopify</a> and <a href="https://www.kickstarter.com/">Kickstarter</a>.
+          battle-tested and trusted by <a href="https://githubengineering.com/the-github-graphql-api/#open-source">GitHub</a>, <a href="https://www.graphql.com/articles/graphql-at-shopify">Shopify</a> and <a href="https://www.kickstarter.com/">Kickstarter</a>.
         </p>
       </div>
     </div>
@@ -72,5 +72,5 @@ <h2>Run Queries</h2>
 </div>
 
 <h3 style="text-align: center;">
-  Add <a href="http://graphql.org">GraphQL</a> to your Ruby app. <a href="{{ site.baseurl}}/getting_started">Get Started!</a>
+  Add <a href="https://graphql.org">GraphQL</a> to your Ruby app. <a href="{{ site.baseurl}}/getting_started">Get Started!</a>
 </h3>

guides/javascript_client/overview.md

@@ -21,7 +21,7 @@ The source code is [in the graphql-ruby repository](https://github.com/rmosolgo/
 
 See detailed guides for more info about its features:
 
-- {% internal_link "sync CLI", "javascript_client/sync" %} for use with [graphql-pro](http://graphql.pro)'s persisted query backend
+- {% internal_link "sync CLI", "javascript_client/sync" %} for use with [graphql-pro](https://graphql.pro)'s persisted query backend
 - Subscription support:
   - {% internal_link "Apollo integration", "/javascript_client/apollo_subscriptions" %}
   - {% internal_link "Relay integration", "/javascript_client/relay_subscriptions" %}

guides/javascript_client/sync.md

@@ -8,7 +8,7 @@ desc: Javascript tooling for persisted queries with GraphQL-Ruby
 index: 1
 ---
 
-JavaScript support for GraphQL projects using [graphql-pro](http://graphql.pro)'s `OperationStore` for persisted queries.
+JavaScript support for GraphQL projects using [graphql-pro](https://graphql.pro)'s `OperationStore` for persisted queries.
 
 - [`sync` CLI](#sync-utility)
 - [Relay support](#use-with-relay)

guides/pro/dashboard.md

@@ -10,7 +10,7 @@ pro: true
 ---
 
 
-[GraphQL-Pro](http://graphql-pro) includes a web dashboard for monitoring {% internal_link "Operation Store", "/operation_store/overview" %} and {% internal_link "subscriptions", "/subscriptions/pusher_implementation" %}.
+[GraphQL-Pro](https://graphql.pro) includes a web dashboard for monitoring {% internal_link "Operation Store", "/operation_store/overview" %} and {% internal_link "subscriptions", "/subscriptions/pusher_implementation" %}.
 
 <!-- TODO image -->
 
@@ -42,7 +42,7 @@ You should only allow admin users to see `/graphql/dashboard` because it allows
 
 ### Rails Routing Constraints
 
-Use [Rails routing constraints](http://api.rubyonrails.org/v5.1/classes/ActionDispatch/Routing/Mapper/Scoping.html#method-i-constraints) to restrict access to authorized users, for example:
+Use [Rails routing constraints](https://api.rubyonrails.org/v5.1/classes/ActionDispatch/Routing/Mapper/Scoping.html#method-i-constraints) to restrict access to authorized users, for example:
 
 ```ruby
 # Check the secure session for a staff flag:

guides/pro/home.md

@@ -1,7 +1,7 @@
 ---
 layout: guide
 doc_stub: false
-outbound_url: http://graphql.pro
+outbound_url: https://graphql.pro
 title: GraphQL::Pro Home
 section: GraphQL Pro
 desc: Overview of GraphQL::Pro features

guides/queries/executing_queries.md

@@ -36,10 +36,10 @@ MySchema.multiplex([
 
 There are also several options you can use:
 
-- `variables:` provides values for `$`-named [query variables](http://graphql.org/learn/queries/#variables)
+- `variables:` provides values for `$`-named [query variables](https://graphql.org/learn/queries/#variables)
 - `context:` accepts application-specific data to pass to `resolve` functions
 - `root_value:` will be provided to root-level `resolve` functions as `obj`
-- `operation_name:` picks a [named operation](http://graphql.org/learn/queries/#operation-name) from the incoming string to execute
+- `operation_name:` picks a [named operation](https://graphql.org/learn/queries/#operation-name) from the incoming string to execute
 - `document:` accepts an already-parsed query (instead of a string), see {{ "GraphQL.parse" | api_doc }}
 - `validate:` may be `false` to skip static validation for this query
 - `max_depth:` and `max_complexity:` may override schema-level values
@@ -48,7 +48,7 @@ Some of these options are described in more detail below, see {{ "GraphQL::Query
 
 ## Variables
 
-GraphQL provides [query variables](http://graphql.org/learn/queries/#variables) as a way to parameterize query strings. If your query string contains variables, you can provide values in a hash of `{ String => value }` pairs. The keys should _not_ contain `"$"`.
+GraphQL provides [query variables](https://graphql.org/learn/queries/#variables) as a way to parameterize query strings. If your query string contains variables, you can provide values in a hash of `{ String => value }` pairs. The keys should _not_ contain `"$"`.
 
 For example, to provide variables to a query:
 

guides/queries/multiplex.md

@@ -8,7 +8,7 @@ desc: Run multiple queries concurrently
 index: 10
 ---
 
-Some clients may send _several_ queries to the server at once (for example, [Apollo Client's query batching](http://dev.apollodata.com/core/network.html#query-batching)). You can execute them concurrently with {{ "Schema#multiplex" | api_doc }}.
+Some clients may send _several_ queries to the server at once (for example, [Apollo Client's query batching](https://www.apollographql.com/docs/react/advanced/network-layer.html#query-batching)). You can execute them concurrently with {{ "Schema#multiplex" | api_doc }}.
 
 Multiplex runs have their own context, analyzers and instrumentation.
 
@@ -56,7 +56,7 @@ def execute
   context = {}
 
   # Apollo sends the params in a _json variable when batching is enabled
-  # see the Apollo Documentation about query batching: http://dev.apollodata.com/core/network.html#query-batching
+  # see the Apollo Documentation about query batching: https://www.apollographql.com/docs/react/advanced/network-layer.html#query-batching
   result = if params[:_json]
     queries = params[:_json].map do |param|
       {

guides/queries/timeout.md

@@ -18,7 +18,7 @@ end
 
 After `max_seconds`, no new fields will be resolved. Instead, errors will be added to the `errors` key for fields that weren't resolved.
 
-__Note__ that this _does not interrupt_ field execution (doing so is [buggy](http://www.mikeperham.com/2015/05/08/timeout-rubys-most-dangerous-api/)). If you're making external calls (eg, HTTP requests or database queries), make sure to use a library-specific timeout for that operation (eg, [Redis timeout](https://github.com/redis/redis-rb#timeouts), [Net::HTTP](https://ruby-doc.org/stdlib-2.4.1/libdoc/net/http/rdoc/Net/HTTP.html)'s `ssl_timeout`, `open_timeout`, and `read_timeout`).
+__Note__ that this _does not interrupt_ field execution (doing so is [buggy](https://www.mikeperham.com/2015/05/08/timeout-rubys-most-dangerous-api/)). If you're making external calls (eg, HTTP requests or database queries), make sure to use a library-specific timeout for that operation (eg, [Redis timeout](https://github.com/redis/redis-rb#timeouts), [Net::HTTP](https://ruby-doc.org/stdlib-2.4.1/libdoc/net/http/rdoc/Net/HTTP.html)'s `ssl_timeout`, `open_timeout`, and `read_timeout`).
 
 To log the error, pass a block to the middleware:
 

guides/queries/tracing.md

@@ -113,7 +113,7 @@ end
 
 ## Skylight
 
-To add [Skylight](http://skylight.io) instrumentation:
+To add [Skylight](https://www.skylight.io) instrumentation:
 
 ```ruby
 class MySchema < GraphQL::Schema

guides/related_projects.md

@@ -11,7 +11,7 @@ Want to add something? Please open a pull request [on GitHub](https://github.com
 
 ## Code
 
-- `graphql-ruby` + Rails demo ([src](https://github.com/rmosolgo/graphql-ruby-demo) / [heroku](http://graphql-ruby-demo.herokuapp.com))
+- `graphql-ruby` + Rails demo ([src](https://github.com/rmosolgo/graphql-ruby-demo) / [heroku](https://graphql-ruby-demo.herokuapp.com))
 - `graphql-ruby` + Sinatra demo ([src](https://github.com/robinjmurphy/ruby-graphql-server-example) / [heroku](https://ruby-graphql-server-example.herokuapp.com/))
 - [`graphql-batch`](https://github.com/shopify/graphql-batch), a batched query execution strategy
 - [`graphql-cache`](https://github.com/stackshareio/graphql-cache), a resolver-level caching solution
@@ -24,7 +24,6 @@ Want to add something? Please open a pull request [on GitHub](https://github.com
   - [`graphql-query-resolver`](https://github.com/nettofarah/graphql-query-resolver), a graphql-ruby add-on to minimize N+1 queries.
   - [`graphql-rails_logger`](https://github.com/jetruby/graphql-rails_logger), a logger which allows you to inspect GraphQL queries in a more readable format.
   - [`apollo_upload_server-ruby`](https://github.com/jetruby/apollo_upload_server-ruby), a middleware which allows you to upload files with GraphQL and multipart/form-data using [`apollo-upload-client`](https://github.com/jaydenseric/apollo-upload-client) library on front-end.
-- [optics-agent-ruby](https://github.com/apollostack/optics-agent-ruby), a graphql-ruby agent for use with the [Apollo Optics](http://www.apollodata.com/optics) GraphQL performance tool.
 - [`search_object_graphql`](https://github.com/rstankov/SearchObjectGraphQL), a DSL for defining search resolvers for GraphQL.
 
 ## Blog Posts

guides/schema/definition.md

@@ -47,7 +47,7 @@ There are lots of schema configuration options:
 
 A GraphQL schema is a web of interconnected types, and it has a few starting points for discovering the elements of that web:
 
-__Root types__ (`query`, `mutation`, and `subscription`) are the [entry points for queries to the system](http://graphql.org/learn/schema/#the-query-and-mutation-types). Each one is an object type which can be connected to the schema by a method with the same name:
+__Root types__ (`query`, `mutation`, and `subscription`) are the [entry points for queries to the system](https://graphql.org/learn/schema/#the-query-and-mutation-types). Each one is an object type which can be connected to the schema by a method with the same name:
 
 ```ruby
 class MySchema < GraphQL::Schema

guides/schema/introspection.md

@@ -9,7 +9,7 @@ class_based_api: true
 index: 2
 ---
 
-A GraphQL schema has a [built-in introspection system](http://graphql.org/learn/introspection/) that publishes the schema's structure. In fact, the introspection system can be queried using GraphQL, for example:
+A GraphQL schema has a [built-in introspection system](https://graphql.org/learn/introspection/) that publishes the schema's structure. In fact, the introspection system can be queried using GraphQL, for example:
 
 ```graphql
 {

guides/schema/root_types.md

@@ -7,7 +7,7 @@ title: Root Types
 desc: Root types are the entry points for queries, mutations and subscriptions.
 ---
 
-GraphQL queries begin from [root types](http://graphql.org/learn/schema/#the-query-and-mutation-types): `query`, `mutation`, and `subscription` (experimental).
+GraphQL queries begin from [root types](https://graphql.org/learn/schema/#the-query-and-mutation-types): `query`, `mutation`, and `subscription` (experimental).
 
 Attach these to your schema using methods with the same name:
 

guides/subscriptions/ably_implementation.md

@@ -9,7 +9,7 @@ index: 7
 pro: true
 ---
 
-[GraphQL Pro](http://graphql.pro) includes a subscription system based on [Redis](http://redis.io) and [Ably](http://ably.io) which works with any Ruby web framework.
+[GraphQL Pro](https://graphql.pro) includes a subscription system based on [Redis](https://redis.io) and [Ably](https://ably.io) which works with any Ruby web framework.
 
 After creating an app on Ably, you can hook it up to your GraphQL schema.
 
@@ -95,7 +95,7 @@ appendonly yes
 
 Otherwise, Redis will drop data that doesn't fit in memory (read more in ["Redis persistence"](https://redis.io/topics/persistence)).
 
-If you're already using Redis in your application, see ["Storing Data in Redis"](http://www.mikeperham.com/2015/09/24/storing-data-with-redis/) for options to isolate data and tune your configuration.
+If you're already using Redis in your application, see ["Storing Data in Redis"](https://www.mikeperham.com/2015/09/24/storing-data-with-redis/) for options to isolate data and tune your configuration.
 
 ## Schema configuration