Jackson error “Illegal character… only regular white space allowed” when parsing JSON

前端 未结 5 2062
刺人心
刺人心 2020-12-17 17:54

I am trying to retrieve JSON data from a URL but get the following error:

Illegal character ((CTRL-CHAR, code 31)):
only regular white space (\\r, \\n,\\t) i         


        
相关标签:
5条回答
  • 2020-12-17 18:22

    I got this same issue, and I found that it was caused by the Content-Encoding: gzip header. The client application (where the exception was being thrown) was not able to handle this content-encoding. FWIW the client application was using io.github.openfeign:feign-core:9.5.0, and this library appears to have some issues around compression (link).

    You might try adding the header Accept-Encoding: identity to your request, however, not all web servers/web applications are configured properly, and some seem to disregard this header. See this question for more details about how to prevent gzipped content.

    0 讨论(0)
  • 2020-12-17 18:25

    We had the same issue in out integration tests recently. We have a spring boot application and we use wiremock to mock a integrated microservice server. For one of the test get requests that we had implemented we started getting this error. We had to downgrade wiremock from 2.18.0 to 2.17.0 and it worked fine. Due to some bug the jackson parser and the that particular version of wiremock didn't work together. We didnt have time to figure out what actually the bug was in those libraries.

    0 讨论(0)
  • 2020-12-17 18:26

    I had the same problem. After setting Gzip it was fixed. Please refer my code

    public String sendPostRequest(String req) throws Exception {
    
        // Create connection
        URL urlObject = new URL(mURL);
        HttpURLConnection connection = (HttpURLConnection) urlObject.openConnection();
        connection.setRequestMethod("POST");
        connection.setRequestProperty("Content-Type", "application/json");
        connection.setRequestProperty("Content-Length", Integer.toString(req.getBytes().length));
        connection.setRequestProperty("Content-Language", "en-US");
        connection.setUseCaches(false);
        connection.setDoOutput(true);
    
        // Send request
        DataOutputStream wr = new DataOutputStream(connection.getOutputStream());
        wr.writeBytes(req);
        wr.close();
    
        //Response handling
        InputStream responseBody                = null;
        if (isGzipResponse(connection)) {
            responseBody                = new GZIPInputStream(connection.getInputStream());         
        }else{
            responseBody = connection.getInputStream();
        }
        convertStreamToString(responseBody);
    
        return response.toString();
    
    }
    
    protected boolean isGzipResponse(HttpURLConnection con) {
        String encodingHeader = con.getHeaderField("Content-Encoding");
        return (encodingHeader != null && encodingHeader.toLowerCase().indexOf("gzip") != -1);
    }
    
    public void convertStreamToString(InputStream in) throws Exception {
        if (in != null) {
    
            ByteArrayOutputStream baos = new ByteArrayOutputStream();
            byte[] buffer = new byte[4096];
            int length = 0;
            while ((length = in.read(buffer)) != -1) {
                baos.write(buffer, 0, length);
            }
    
            response = new String(baos.toByteArray());
    
            baos.close();
    
        } else {
            response = null;
        }
    
    }
    
    0 讨论(0)
  • 2020-12-17 18:38

    I had a similar issue. After some research, I found of that restTemplate uses the SimpleClientHttpRequestFactory which does not support gzip encoding. To enable gzip encoding for your response, you will need to set a new request factory for the rest template object - HttpComponentsClientHttpRequestFactory.

    restTemplate.setRequestFactory(new HttpComponentsClientHttpRequestFactory());

    0 讨论(0)
  • 2020-12-17 18:40

    The message should be pretty self-explanatory:

    There is an illegal character (in this case character code 31, i.e. the control code "Unit Separator") in the JSON you are processing.

    In other words, the data you are receiving is not proper JSON.


    Background:

    The JSON spec (RFC 7159) says:

    1. JSON Grammar

    A JSON text is a sequence of tokens. The set of tokens includes six tructural characters, strings, numbers, and three literal names.

    [...]

    Insignificant whitespace is allowed before or after any of the six structural characters.

    ws = *(

    %x20 / ; Space

    %x09 / ; Horizontal tab

    %x0A / ; Line feed or New line

    %x0D ) ; Carriage return

    In other words: JSON may contain whitespace between the tokens ("tokens" meaning the part of the JSON, i.e. lists, strings etc.), but "whitespace" is defined to only mean the characters Space, Tab, Line feed and Carriage return.

    Your document contains something else (code 31) where only whitespace is allowed, hence is not valid JSON.


    To parse this:

    Unfortunately, the Jackson library you are using does not offer a way to parse this malformed data. To parse this successfully, you will have to filter the JSON before it is handled by Jackson.

    You will probably have to retrieve the (pseudo-)JSON yourself from the REST service, using standard HTTP using, e.g. java.net.HttpUrlConnection. Then suitably filter out "bad" characters, and pass the resulting string to Jackson. How to do this exactly depends on how you use Jackson.

    Feel free to ask a separate questions if you are having trouble :-).

    0 讨论(0)
提交回复
热议问题