RestSharp和Twitter API 1.1：我如何正確URLEncode狀態更新文本？

Question

我正在嘗試使用RestSharp從我的網絡應用發佈Twitter狀態。下面的代碼工作完美：

var status = "I am fine with posting this status."; 

var client = new RestClient("https://api.twitter.com"); 

// The OAuth keys/tokens/secrets are retrieved elsewhere 
client.Authenticator = OAuth1Authenticator.ForProtectedResource(
    _consumerKey, _consumerSecret, _accessToken, _accessTokenSecret 
); 

var request = new RestRequest("/1.1/statuses/update.json", Method.POST); 
request.AddParameter("status", status, ParameterType.GetOrPost); 

var response = client.Execute(request); 

但是，此代碼失敗，身份驗證錯誤，如果我有任何的狀態文本如下字符：! * ' ()

通過論壇拖網的很多，我已經推斷出這與OAuth簽名編碼不匹配POST參數的編碼有關。我發現this question on SO，但在GitHub上搜索RestSharp問題沒有任何幫助。

我可以看到some code in the RestSharp source（UrlEncodeRelaxed）這似乎是手動編碼的特定字符集合符合OAuth編碼規範，所以我試圖以相同的方式手動編碼這些字符在我的狀態（帶代碼來自RestSharp），例如：

var status = "I'm NOT fine with posting this status."; 

string[] UriRfc3986CharsToEscape = new[] { "!", "*", "'", "(", ")" }; 
string[] UriRfc3968EscapedHex = new[] { "%21", "%2A", "%27", "%28", "%29" }; 

for (var i = 0; i < UriRfc3986CharsToEscape.Length; i++) 
    status = status.Replace(UriRfc3986CharsToEscape[i], UriRfc3968EscapedHex[i]); 

但是這也行不通（我仍然得到認證錯誤）。

這裏的問題實際上是什麼，以及我應該如何正確編碼狀態？或者這是一個RestSharp錯誤？

Answer 1

您是否嘗試過使用內置於.NET Framework的HttpUtility類？你可以在System.Web命名空間中找到它。

string urlEncodedText = HttpUtility.UrlEncode("Your text goes here"); 

MSDN

---

這絕對是一個RestSharp問題......我用它玩了一段時間，問題是，有沒有反正禁用標準百分號編碼.. 。

void Main() 
{ 
    var ProtectedChars = "0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39, 0x41, 0x42, 0x43, 0x44, 0x45, 0x46, 0x47, 0x48, 0x49, 0x4A, 0x4B, 0x4C, 0x4D, 0x4E, 0x4F, 0x50, 0x51, 0x52, 0x53, 0x54, 0x55, 0x56, 0x57, 0x58, 0x59, 0x5A, 0x61, 0x62, 0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x6A, 0x6B, 0x6C, 0x6D, 0x6E, 0x6F, 0x70, 0x71, 0x72, 0x73, 0x74, 0x75, 0x76, 0x77, 0x78, 0x79, 0x7A".Replace(" 0x", "%").Split(','); 
    var client = new RestClient("https://api.twitter.com"); 

    client.Authenticator = OAuth1Authenticator.ForProtectedResource(
     "_consumerKey", "_consumerSecret", "_accessToken", "_accessTokenSecret" 
    ); 

    var status = "Dogs, Cats & Mice"; 

    string newStatus = string.Empty; 

    foreach (char c in status) 
    { 
     var charBytes = Encoding.UTF8.GetBytes(c.ToString()); 
     var tempText = string.Empty; 

     for (int i = 0; i < charBytes.Count(); i++) 
     { 
      byte b = charBytes[i]; 
      string hex = "%" + b.ToString("X2"); 
      tempText += hex; 
     } 

     if (ProtectedChars.Any(x => x == tempText)) 
     { 
      newStatus += c; 
     } 
     else 
     { 
      newStatus += string.Format("{0:X2}", tempText); 
     } 
    } 

    var request = new RestRequest("/1.1/statuses/update.json", Method.POST); 
    request.AddParameter(new Parameter{ Name = "status", Type = ParameterType.GetOrPost, Value = newStatus }); 

    var response = client.Execute(request); 


} 

在菲德勒我一直在監測將Twitter上的要求......這是我發現了什麼......

POST https://api.twitter.com/1.1/statuses/update.json HTTP/1.1 
Authorization: /* auth data */ 
Accept: application/json, application/xml, text/json, text/x-json, text/javascript, text/xml 
User-Agent: RestSharp/104.4.0.0 
Content-Type: application/x-www-form-urlencoded 
Host: api.twitter.com 
Content-Length: 44 
Accept-Encoding: gzip, deflate 

status=Dogs%252C%2520Cats%2520%2526%2520Mice 

Http請求的問題是我們請求的主體...如果我提供的價值沒有被觸及...那麼Twitter會識別出消息並更新我們的狀態....

status=Dogs%252C%2520Cats%2520%2526%2520Mice <--- Altered by RestSharp 
status=Dogs%2C%20Cats%20%26%20Mice   <--- What I initially sent