Changes between Version 11 and Version 12 of FAQs


Ignore:
Timestamp:
2014-02-04T08:14:03Z (11 years ago)
Author:
Pan Luo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQs

    v11 v12  
    6969}}}
    7070
    71 Logging the raw message will reveal that the response message has been chunked with a leading number and ending 0 (http://en.wikipedia.org/wiki/Chunked_transfer_encoding). This cause !RestTemplate doesn't recognize the response and throw the exception. And this has been seen when server is set up with Apache + mod_php + Nginx (1.0.15) Proxy on RHEL 6.5.
     71Logging the raw message reveals that the response message has been chunked with a leading number (something like 28f4) and an ending 0 (http://en.wikipedia.org/wiki/Chunked_transfer_encoding). This cause !RestTemplate couldn't parse the response json correctly and throw the exception. And this has been seen when server is set up with Apache + mod_php + Nginx (1.0.15) Proxy on RHEL 6.5.
    7272
    7373There are several ways to solve this problem:
    7474* Quick workaround: Adding "chunked_transfer_encoding off;" in nginx configuration file to disable the chunked transfer encoding feature.
    7575* A patch has been added to iPeer code base to avoid the response being chunked. This patch will be included in version 3.1.1.
    76 * (Figure out why RestTemplate is not correct parsing chunked response.)
     76* (Figure out why !RestTemplate is not correct parsing chunked response.)