为什么凌空的响应字符串中使用的编码从在响应头有什么不同?字符串、有什么不同

2023-09-12 08:10:17 作者:孤独患者

在做一个凌空请求(无论是 StringRequest JsonObjectRequest ),使用OkHttp栈,响应字符串的编码设置为ISO-8995-1,这是默认的编码。响应有一个标题:的content-type = text / html的;字符集= UTF-8 ,这应该被检测到。为什么不呢?

When doing a volley request (either StringRequest or JsonObjectRequest), using the OkHttp stack, the response string's encoding is set to ISO-8995-1, which is the default encoding. The response has a header: content-type=text/html; charset=utf-8, which should be detected. Why isn't it?

推荐答案

这两方面的请求类型调用 HttpHeaderParser.parseCharset ,它能够确定从标题的字符集。然而,它要求标题为内容类型,不是内容类型:它是区分大小写。 (我不知道的行为,如果使用默认HurlStack,这是可能的,这是与OkHttp栈的实现细节的差异。)

Both of those request types call HttpHeaderParser.parseCharset, which is able to determine the charset from the headers. However, it requires that the header be Content-Type, not content-type: it is case sensitive. (I'm not sure of the behavior if using the default HurlStack, it's possible this is an implementation detail difference with the OkHttp stack.)

解决方法1:复制原始请求类型,但手动覆盖字符集

Solution 1: copy the original request type, but manually override the charset

解决方法2:复制原始请求类型,但强制预计头存在

Solution 2: copy the original request type, but force the expected header to exist

import com.android.volley.NetworkResponse;
import com.android.volley.ParseError;
import com.android.volley.Response;
import com.android.volley.Response.ErrorListener;
import com.android.volley.Response.Listener;
import com.android.volley.toolbox.HttpHeaderParser;
import com.android.volley.toolbox.JsonRequest;

import org.json.JSONException;
import org.json.JSONObject;

import java.io.UnsupportedEncodingException;

public class JsonUTF8Request extends JsonRequest<JSONObject> {
    public JsonUTF8Request(int method, String url, JSONObject jsonRequest,
                           Listener<JSONObject> listener, ErrorListener errorListener) {
        super(method, url, (jsonRequest == null) ? null : jsonRequest.toString(), listener,
                errorListener);
    }

    @Override
    protected Response<JSONObject> parseNetworkResponse(NetworkResponse response) {
        try {
            // solution 1:
            String jsonString = new String(response.data, "UTF-8");
            // solution 2:
            response.headers.put(HTTP.CONTENT_TYPE,
                response.headers.get("content-type"));
            String jsonString = new String(response.data, HttpHeaderParser.parseCharset(response.headers));
            //
            return Response.success(new JSONObject(jsonString),
                    HttpHeaderParser.parseCacheHeaders(response));
        } catch (UnsupportedEncodingException e) {
            return Response.error(new ParseError(e));
        } catch (JSONException je) {
            return Response.error(new ParseError(je));
        }
    }
}