#1152 Fixed 100-continue handling
Merge branch '1152-21x-100-continue' into 2.1.x
Fixed Issue #1111: Broken image link in docs | (ammended)
Replaced image source with the correct relative raw URL.
I payed attention to refer the one from the 2.1.x branch.
Fixeding build
Added API docs deployment
Merge pull request #1287 from kovacshuni/Play20-1111

Fixed Issue #1111: Broken image link in docs
Fix dead link to requirejs "Next" page.

This is already fixed in master, but adding to 2.1 branch.
Merge pull request #1311 from wsargent/patch-1

Fix dead link to requirejs "Next" page.
Fixed a regression that resulted in the action body being executed on the iteratee execution context, and not the users:

https://github.com/playframework/Play20/commit/7e58680e44890b5d0a292d0f98fcc6bf936e3c4d#commitcomment-3584037
Fix in relation to issue #1332. It appears as though connection failures were not permitting an iteratee to be completed. This caused a particular issue with respect to chunked replies.
 #1329 Improved spec compliance with etags

- RFC2616 requires that if an etag is given with the If-None-Match
  header, but doesn't match, then the If-Modified-Since header must be
  ignored.
- This was causing issues specifically when rolling back a deployment.
- Also moved the AssetsSpec out of the integrationtest project and into
  play-integration-test, to make it simpler.
Switch to using ActorSystem.dispatchers.defaultGlobalDisptacher

Akka 2.2 changed the return type of ActorSystem.dispatcher from being
MessageDispatcher to being the less specific ExecutionContext
(ExecutionContext is a super type of MessageDispatcher).  This is the
only binary compatibility breaking change for Play, and so is the only
thing preventing users from upgrading to Akka 2.2.

The implementation of ActorSystem.dispatcher is
ActorSystem.dispatchers.defaultGlobalDispatcher.  The method signatures
of these methods haven't changed between 2.1 and 2.2, so be switching to
using them instead, we can allow Play users to upgrade to Akka 2.2 at
their own leisure.

Please note, this change does not upgrade Play to Akka 2.2, it only
makes Play binary compatible with both Akka 2.1 and Akka 2.2, so that
users can at their option upgrade to Akka 2.2.