GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/616
Ts 4401
I've split this into four commits (two cleanup, two features):
1) Modify the clang-format for a couple of initializers, by appending a
trailing ,. This is the recommended way from clang-format to enforce this
behavior (they opted not to have a config).
2) Reordered some switch statements, to follow the enum cardinality.
3) Make proxy.config.http.uncacheable_requests_bypass_parent overridable.
4) Make proxy.config.http.parent_proxy.total_connect_attempts overridable.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4401
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/616.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #616
----
commit b062368dbc89cf90977f498f7e4ed2277aa0fd3f
Author: Leif Hedstrom <[email protected]>
Date: 2016-04-30T18:10:09Z
TS-4401 Fix clang-format indentation
commit 4f199d38ddacd8b1b0be7f73ce1e9e1e6df68713
Author: Leif Hedstrom <[email protected]>
Date: 2016-04-30T18:10:26Z
TS-4401 Cleanup of the overridable switch statement
This does two things:
1) It fixes a couple of places where the type is set to
MgmtInt, when in reality they are MgmtByte's (and vice
versa).
2) Reorder the case statements, to be inline with the
cardinality of the enum type.
commit 06a3401ed3ea0ca7decfb5f650b6e3bcae018a82
Author: Leif Hedstrom <[email protected]>
Date: 2016-04-30T18:58:58Z
TS-4401 Override proxy.config.http.uncacheable_requests_bypass_parent
commit e93be91d5e1b7979172f87019c7924fdecee8192
Author: Leif Hedstrom <[email protected]>
Date: 2016-04-30T22:16:32Z
TS-4401 Override proxy.config.http.parent_proxy.total_connect_attempts
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
