Add failure handlers to test calls.
Merge pull request #1697 from carsonmcdonald/capturetestfailures

Add failure handlers to test calls.
Ignoring -Wunused-parameter for AFContentTypeForPathExtension
Enabling additional warnings
Merge branch 'master' of github.com:AFNetworking/AFNetworking
[Issue #1701] Validating responses of download tasks
A couple of changes to `AFInflatedImageFromResponseWithDataAtScale`:

1. `CGImageCreateWithJPEGDataProvider` does not properly handle CMYK images, so if CMYK image, fall back to `AFImageWithDataAtScale`, which handles CMYK JPEG images properly.

2. `CGBitmapContextCreate` does not handle 16 or 32 npc images properly (or at least it generates warning), so abort inflate process if more than 8 bpc.

3. Simplify the invocation of `CGDataProviderRelease` so we only have it in one place.

4. Previous incarnation of `AFInflatedImageFromResponseWithDataAtScale` could, in some circumstances, make redundant calls to `AFImageWithDataAtScale`, so tweaked the logic to remove these redundant calls.

5. This routine was manipulating the alpha settings in `bitmapInfo` if the colorspace had three components. Technically, because there are other colorspaces with three components (e.g. Lab), it’s probably more prudent to check to see if the colorspace is RGB.
Minor stylistic edits; remove extraneous `CGImageRelease` error

Use `NULL` for initialization of `CGImageRef`; remove unnecessary initialization of `UIImage`; remove confusing reference to `bytesPerRow` and the now obsolete iOS 5 reference; remove extraneous (and incorrect) `CGImageRelease`
Update CONTRIBUTING.md
Update CONTRIBUTING.md
Removing unnecessary != NULL for error pointer check, for consistency
Merge branch 'master' of github.com:AFNetworking/AFNetworking
Fix warning about weak receiver being set to nil, capture strong reference.
[Issue #1735] Fixing dead store issues in AFSecurityPolicy.m

Build and analyze yields the following issues when assertions are enabled:

```
AFNetworking/AFSecurityPolicy.m:123:18: Value stored to 'status' during its initialization is never read
AFNetworking/AFSecurityPolicy.m:127:9: Value stored to 'status' is never read
```

This patch mimics the pattern established previously in this file on line 89. It adds a check for whether NS_BLOCK_ASSERTIONS is defined to determine whether to use the status variable.
Update README.md: multi-part upload task example

I found the documentation lacking an example of how to do multi-part uploads with feedback through NSProgress.
Specifically the crucial connection between multi-part upload and `uploadTaskWithStreamedRequest:progress:completionHandler:`.

However, as it was not working correctly until https://github.com/AFNetworking/AFNetworking/pull/1617 this change could probably be included at the same time as that change is "released".
NSURLConnectionDelegate should be NSURLConnectionDataDelegate
Merge pull request #1748 from dpassage/setredirectresponseblockdocs

NSURLConnectionDelegate should be NSURLConnectionDataDelegate
[Issue # 1661][Issue #1633][Issue #1745][Issue #1731] Initializing managers with default reachability manager, and not starting on initialization
Merge branch 'master' of github.com:AFNetworking/AFNetworking
Merge pull request #1742 from johanforssell/patch-1

Update README.md: multi-part upload task example