[URL Operation] Use the ivar directly in initialization

This is to prevent calling the custom setter inside initialization which
broadcasts KVO notifications and relies on existing state which isn't
yet setup.

Re #1845
[URL Operation] Don't allow transitioning to invalid states
Use "long long" instead of "NSInteger" on byte count.

Byte count should always be 64bit integer. Otherwise, AFNetworking won't work on streams
larger than 4GB in 32bits mode. This commit revert the PR #1772 and e94a52c.
Added test to check content type
Explicitly importing MobileCoreServices.
Fixes failing test
Update license year

Fix outdated copyright year (updated to 2014).
The copyright year was out of date. Copyright notices must reflect the current year, so this commit updates the listed year to 2014.

See http://www.copyright.gov/circs/circ01.pdf for more info.
care for 'Content-Length'  on taskDidSendBodyData block
Use SecTrust return status code at runtime

The `SecTrust` functions in use within AFSecurityPolicy.h only make use of the return code when `NS_BLOCK_ASSERTIONS` is not defined. The use of NS_BLOCK_ASSERTIONS to silence static analyzer warnings about unused values is convenient, however the larger issue is the failure of `AFPublicKeyForCertificate`, `AFPublicKeyTrustChainForServerTrust` and `AFServerTrustIsValid` to detect a runtime status code that is not `errSecSuccess` and to return early.
Merge pull request #1878 from kylef/state_setter

[URL Operation] Use the ivar directly in initialization
Adding necessary diagnostic ignore #pragma statements
Merge pull request #1896 from dtorres/MIMETYPE-TEST

Added test to check content type
[Issue #1961] Changing HTTP manager method signatures to accept parameters as id type
Merge branch 'master' of github.com:AFNetworking/AFNetworking
Merge pull request #1962 from RobotsAndPencils/SecTrustErrorHandling

Use SecTrust return status code at runtime
[Issue #1962] Refactoring security policy to use assertion macros to DRY up cleanup code
Fixing not calling taskDidComplete if there's no task delegate.
Fix 64-bit iOS unit tests

Under 64-bit iOS, the `BOOL` type has changed from `signed char` to `bool` but NSNumber did not get the memo. So [@NO objCType] (which is equivalent to [[NSNumber numberWithBool:NO] objCType]) returns "c" (_C_CHR) instead of "B" (_C_BOOL). OCMock uses this information to check that the mock return type is compatible with the expected return type. Using the OCMOCK_VALUE macro solves the problem since it explicitly encodes the `BOOL` type.
Update the App.net certificate

App.net recently updated their certificate, maybe because of the Heartbleed bug. Since the example app does certificate pinning it stopped working as the certificate did not match.
Update the App.net API base URL
Re-establish AFNetworkingURLSessionTaskDelegates after restoring from a specific configuration.  Create accessors for getting download an upload progress objects from tasks.