Add setCipher method.

BigCommerce/Api.php

@@ -73,6 +73,14 @@ public static function verifyPeer($option=false)
 		self::connection()->verifyPeer($option);
 	}
 
+	/**
+	 * Set which cipher to use during SSL requests.
+	 */
+	public static function setCipher($cipher='RC4-SHA')
+	{
+		self::connection()->setCipher($cipher);
+	}
+
 	/**
 	 * Connect to the internet through a proxy server.
 	 *
@@ -684,4 +692,4 @@ public static function getRequestsRemaining()
 		return intval($limit);
 	}
 
-}
+}

BigCommerce/Api/Connection.php

@@ -156,6 +156,15 @@ public function verifyPeer($option=false)
 		curl_setopt($this->curl, CURLOPT_SSL_VERIFYPEER, $option);
 	}
 
+	/**
+	 * Set which cipher to use during SSL requests.
+	 * @param string $cipher the name of the cipher
+	 */
+	public function setCipher($cipher='RC4-SHA')
+	{
+		curl_setopt($this->curl, CURLOPT_SSL_CIPHER_LIST, $cipher);
+	}
+
 	/**
 	 * Add a custom header to the request.
 	 */
@@ -487,4 +496,4 @@ public function __toString()
 class BigCommerce_Api_ServerError extends BigCommerce_Api_Error
 {
 
-}
+}

README.md

@@ -273,6 +273,18 @@ The exceptions thrown are subclasses of BigCommerce_Api_Error, representing
 client errors and server errors. The API documentation for response codes
 contains a list of all the possible error conditions the client may encounter.
 
+Specifying the SSL cipher
+-------------------------
+
+The API requires that all client SSL connections use the rsa_rc4_128_sha cipher.
+This should not be an issue as curl will use this by default. In those
+situations where this is not the case the you will need to use the setCipher
+method to force curl to use the correct cipher.
+
+```
+BigCommerce_Api::setCipher('RC4-SHA');
+```
+
 Verifying SSL certificates
 --------------------------