TykTechnologies / tyk / 4460 / 1

Ran 23 Mar 2018 02:48PM UTC

Files 89

Run time 3s

Badge

Embed ▾

Committed 23 Mar 2018 02:42PM UTC coverage: 55.422% (+0.01%) from 55.41%

Job # LATEST_GO=true

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

Separate client keep alive and proxy keepalive options (#1561)

In 2.5 we (I), introduced confusing change, and `connection_close` option started to disable proxy keepalives in addition to client keepalives. This brings a lot of confusion since we recommend setting `connection_close` in production environments.

This change rollbacks `connection_close` behavior: now it controls only client keepalives. And additionally, it disables keep alive on tyk server level, so even if clients do not obey `Connection: close` header, the connection will be closed anyway.

Added new option called `proxy_connection_close`, which controls keep alive behavior between tyk and upstream.  

Should fix https://github.com/TykTechnologies/tyk/issues/1565

Run Details

7952 of 14348 relevant lines covered (55.42%)

0.61 hits per line

TykTechnologies / tyk / 4460 / 1

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4460.1 (LATEST_GO=true)

TykTechnologies / tyk / 4460 / 1

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4460.1 (LATEST_GO=true)

README BADGES
x