Changes between Version 11 and Version 12 of FAQs
- Timestamp:
- 2014-02-04T08:14:03Z (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FAQs
v11 v12 69 69 }}} 70 70 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 responseand 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.71 Logging 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. 72 72 73 73 There are several ways to solve this problem: 74 74 * Quick workaround: Adding "chunked_transfer_encoding off;" in nginx configuration file to disable the chunked transfer encoding feature. 75 75 * 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.)