452a7ae88b
Currently HttpClient sends requests for JSON data with the XMLHttpRequest.responseType set to 'json'. With this flag, the browser will attempt to parse the response as JSON, but will return 'null' on any errors. If the JSON response contains an XSSI-prevention prefix, this will cause the browser's parsing to fail, which is unrecoverable. The only compelling reason to use the responseType 'json' is for performance (especially if the browser offloads JSON parsing to a separate thread). I'm not aware of any browser which does this currently, nor of any plans to do so. JSON.parse and responseType 'json' both end up using the same V8 code path in Chrome to implement the parse. Thus, this change switches all JSON parsing in HttpClient to use JSON.parse directly. Fixes #18396, #18453. PR Close #18466 |
||
|---|---|---|
| .. | ||
| client_spec.ts | ||
| headers_spec.ts | ||
| jsonp_mock.ts | ||
| jsonp_spec.ts | ||
| module_spec.ts | ||
| params_spec.ts | ||
| request_spec.ts | ||
| response_spec.ts | ||
| xhr_mock.ts | ||
| xhr_spec.ts | ||
| xsrf_spec.ts | ||