Back to bug 1316463
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Miciah Dashiel Butler Masters | 2016-03-10 17:41:38 UTC | Status | NEW | ASSIGNED |
| Meng Bo | 2016-05-12 02:32:44 UTC | Keywords | NeedsTestCase | |
| CC | bmeng | |||
| Miciah Dashiel Butler Masters | 2016-06-03 12:55:54 UTC | Status | ASSIGNED | MODIFIED |
| zhaozhanqi | 2016-08-24 03:25:51 UTC | Keywords | NeedsTestCase | |
| Troy Dawson | 2016-09-01 15:26:53 UTC | CC | tdawson | |
| errata-xmlrpc | 2016-09-01 15:44:29 UTC | Status | MODIFIED | ON_QA |
| Hongan Li | 2016-09-02 09:51:27 UTC | Status | ON_QA | VERIFIED |
| CC | hongli | |||
| Miciah Dashiel Butler Masters | 2016-09-14 18:54:05 UTC | Target Release | --- | 3.3.0 |
| Doc Text | Cause: The F5 iControl REST API usually returns JSON payloads in its responses, but it sometimes returns error responses with HTML payloads. In particular, it can return HTML payloads with HTTP 401 and 404 responses. Previously, the router would always try to decode the payload as JSON. Consequence: If the F5 iControl REST API returned an HTML response, the router logs would show the following: "error: Decoder.Decode failed: invalid character '<' looking for beginning of value". Fix: The F5 router plugin now gracefully handles HTML responses by ignoring the response payload for HTTP 4xx and 5xx responses if decoding as JSON fails. Result: If the F5 iControl REST API returns an HTML response, the router logs will now show a message similar to the following: "error: HTTP code: 401." |
|||
| errata-xmlrpc | 2016-09-27 00:23:45 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-09-27 09:36:16 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-09-27 05:36:16 UTC | |||
| Dan McPherson | 2017-03-08 18:26:17 UTC | Target Release | 3.3.0 | |
| Miciah Dashiel Butler Masters | 2022-08-04 22:20:48 UTC | Component | Routing | Networking |
| Sub Component | router |
Back to bug 1316463