Question

我尝试使用改装来致电Kraken API。我有一个工作AsyncHttpClient版本，我想转换为改装版本，我在传递POST参数方面遇到了一些问题。

如需要的文件中所述：

2个HTTP标头：API-Key和API-Sign。
POST数据：nonce
端点的2个输入参数我呼叫：start和ofs

AsyncHttpClient 版本（正常）：

String start = String.valueOf(cal.getTimeInMillis() / 1000);
String key = properties.getProperty("KRAKEN_API_PUBLIC_KEY");
String nonce = String.valueOf(System.currentTimeMillis());
String path = "/0/private/TradesHistory";

RequestParams params = new RequestParams();
params.add("nonce", nonce);
params.add("start", start);
params.add("ofs", String.valueOf(offset));

String sign = calculateSignature(path, nonce, params.toString());

AsyncHttpClient client = new AsyncHttpClient();
client.addHeader("API-Key", key);
client.addHeader("API-Sign", sign);

client.post("https://api.kraken.com"+ path, params, new JsonHttpResponseHandler() {
    @Override
    public void onSuccess(int statusCode, Header[] headers, JSONObject response) {
        // works
    }
});

改造版本（EAPI:Invalid key响应）：

String start = String.valueOf(cal.getTimeInMillis() / 1000);
String key = properties.getProperty("KRAKEN_API_PUBLIC_KEY");
String nonce = String.valueOf(System.currentTimeMillis());
String path = "/0/private/TradesHistory";

RequestParams params = new RequestParams();
params.add("nonce", nonce);
params.add("start", start);
params.add("ofs", String.valueOf(offset));

String sign = calculateSignature(path, nonce, params.toString());

KrakenService krakenService = KrakenService.retrofit.create(KrakenService.class);
Call<KrakenTrades> call = krakenService.getTradeHistory(key, sign, nonce, start, String.valueOf(offset));
call.enqueue(new Callback<KrakenTrades>() {
    @Override
    public void onResponse(@Nullable Call<KrakenTrades> call, @Nullable Response<KrakenTrades> response) {
        // EAPI:Invalid key
    }
});

服务：

public interface KrakenService {

    @FormUrlEncoded
    @POST("private/TradesHistory")
    Call<KrakenTrades> getTradeHistory(
        @Header("API-Key") String apiKey,
        @Header("API-Sign") String apiSign,
        @Field("nonce") String nonce,
        @Field("start") String start,
        @Field("ofs") String ofs);

    Retrofit retrofit = new Retrofit.Builder()
        .baseUrl("https://api.kraken.com/0/")
        .addConverterFactory(GsonConverterFactory.create())
        .build();
}

只有通话不同，我会错过什么吗？我已尝试使用@query，@Body，@FieldMap，@HeaderMap等，但无法使其正常运行。

编辑：我刚尝试使用Poloniex之类的其他API并遇到了同样的问题（无效密钥），但它仍适用于基本的HTTPClient。

Answer 1

如果您对其他API持开放态度，请让我建议mesibo，它使用起来要简单得多，

mesibo.Http http = new mesibo.Http();

Bundle b = new Bundle();
b.putString("token", "some_token");
b.putLong("mid", mid);


http.url = “https://example.com”;
http.postBundle = b;
http.other = myObject; // callback data

http.onMainThread = true; // invoke listener in main thread
http.listener = new mesibo.HttpListener() {
    @Override
    public boolean mesibo_onHttpProgress(mesibo.Http http, int state, int percent) {
        if(100 == percent && mesibo.Http.STATE_DOWNLOAD == state) {
                // download complete
        }

        Return true; // return false to cancel
    }
};

if(http.execute()) {

}

Answer 2

我设法让它发挥作用，但我不得不承认我没有明白这一点......

我已激活OkHttp日志以查看请求。这是我首先得到的（这些假钥匙不会丢失你的时间-_-）：

D/OkHttp: --> POST https://api.kraken.com/0/private/TradesHistory http/1.1
D/OkHttp: Content-Type: application/x-www-form-urlencoded
D/OkHttp: Content-Length: 42
D/OkHttp: API-Sign: /Eu6Sth0oa13Tr/ofme07TF4ct+TercW7uU9PxBEQhcpYTflC2c/jEW1BZuamBXco0jlgOzWt8RMh0o6kAE5SA==
D/OkHttp: API-Key: XnmS2gW2Sr1xR/vnB0ivJuHABdXUnW4bsMTOBMREOlz8xYDh00J+D9i4
D/OkHttp: start=1481587200&ofs=0&nonce=1511301862261
D/OkHttp: --> END POST (42-byte body)
D/OkHttp: <-- 200  https://api.kraken.com/0/private/TradesHistory (2049ms)
D/OkHttp: date: Tue, 21 Nov 2017 22:04:27 GMT
D/OkHttp: content-type: application/json; charset=utf-8
D/OkHttp: set-cookie: __cfduid=dc9e29889eeda633314ca5aaad10ce8291511301865; expires=Wed, 21-Nov-18 22:04:25 GMT; path=/; domain=.kraken.com; HttpOnly
D/OkHttp: vary: Accept-Encoding
D/OkHttp: server: cloudflare-nginx
D/OkHttp: cf-ray: 3c16f1d348503e80-ZRH
D/OkHttp: {"error":["EAPI:Invalid key"]}
D/OkHttp: <-- END HTTP (30-byte body)

现在，我没有使用params.toString()作为参数来计算签名，而是通过手动连接的值（"start=" + start + "&ofs=" + offset +"&nonce=" + nonce），这就是我得到的：

D/OkHttp: --> POST https://api.kraken.com/0/private/TradesHistory http/1.1
D/OkHttp: Content-Type: application/x-www-form-urlencoded
D/OkHttp: Content-Length: 42
D/OkHttp: API-Sign: DuxyUuHbj4V9WrOpaoBM6Rx3mZluoqJdkg3xBLgc0A/lVotq3WL19VErctz+ugTxi0eRpCI6oBnl95+Lmh9WmQ==
D/OkHttp: API-Key: XnmS2gW2Sr1xR/vnB0ivJuHABdXUnW4bsMTOBMREOlz8xYDh00J+D9i4
D/OkHttp: start=1481587200&ofs=0&nonce=1511302135971
D/OkHttp: --> END POST (42-byte body)
D/OkHttp: <-- 200  https://api.kraken.com/0/private/TradesHistory (1340ms)
D/OkHttp: date: Tue, 21 Nov 2017 22:09:04 GMT
D/OkHttp: content-type: application/json; charset=utf-8
D/OkHttp: set-cookie: __cfduid=d7916fbb113ed6f83b9382ea0a57240731511302143; expires=Wed, 21-Nov-18 22:09:03 GMT; path=/; domain=.kraken.com; HttpOnly
D/OkHttp: vary: Accept-Encoding
D/OkHttp: server: cloudflare-nginx
D/OkHttp: cf-ray: 3c16f89b4e273e62-ZRH
D/OkHttp: {"error":[],"result":{"trades":{...}}}
D/OkHttp: <-- END HTTP (11944-byte body)

查看发送数据的差异？没有？没有......

但它确实有效，而且我再也没有得到invalid key回复了。

另一个奇怪的事情是，更改参数的顺序会使其回退到invalid key响应：

String parameters = "start=" + start + "&ofs=" + offset +"&nonce=" + nonce; //works
String parameters = "start=" + start + "&nonce=" + nonce + "&ofs=" + offset; //doesn't work

我无法解释这个......也许编码问题？

编辑：好了，似乎参数在请求正文中排序。虽然服务器不关心HTTP参数的顺序，但HMAC（当然param1=value1&param2=value2会生成与param2=value2&param1=value1不同的HMAC）。

所以我必须在用于计算HMAC的字符串中使用与请求体中完全相同的顺序（我从OkHttp日志中获取的顺序硬编码了值，但最好的方法是从中提取它请求正文，甚至更好地规范请求正文。）

改造 - 传递POST参数数据和标题

2 个答案: