|
Ran
|
Jobs
2
|
Files
82
|
Run time
1min
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/TykTechnologies/tyk/commit/<a class=hub.com/TykTechnologies/tyk/commit/52163e7211f6426ec33cc556e859833d201f68ab">52163e721<a href="https://github.com/TykTechnologies/tyk/commit/52163e7211f6426ec33cc556e859833d201f68ab">">Fix handling of broken HTTP clients (#1979) Clients who close connection before reading response, cause 500 error in gateway analytics In this specific case Gateway itself did the right job and proxied the request, it is the client who messes with the connection. This is still an error state, but there should be a way to differentiate such issues from server-side ones. In this cases we introduce special 499 code (same as Nginx has), which description is: ``` 499 Client Closed Request Used when the client has closed the request before the server could send a response. ``` Fix https://github.com/TykTechnologies/tyk/issues/1980 (cherry picked from commit </a><a class="double-link" href="https://github.com/TykTechnologies/tyk/commit/<a class="double-link" href="https://github.com/TykTechnologies/tyk/commit/fa93f7bc8c091f6f97720eea6787664b5f4bba45">fa93f7bc8</a>">fa93f7bc8</a><a href="https://github.com/TykTechnologies/tyk/commit/52163e7211f6426ec33cc556e859833d201f68ab">)
8938 of 14636 relevant lines covered (61.07%)
1.35 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 6003.1 (LATEST_GO=true) | 0 |
60.54 |
Travis Job 6003.1 | |
| 2 | 6003.2 (LATEST_GO=true) | 0 |
61.06 |
Travis Job 6003.2 |