[ 
https://issues.apache.org/jira/browse/TS-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728659#comment-13728659
 ] 

ASF subversion and git services commented on TS-1255:
-----------------------------------------------------

Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from 
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]

Merge branch 'master' into 3.3.x

* master: (295 commits)
  TS-2081 Make the WCCP addr configuration LOCAL
  TS-2093: Check bounds on plugin stat creation.
  TS-2092 Use of uninitialized member in HdrHeap.
  [TS-2052] ET_SSL thread spinning
  TS-2090 Make proxy.config.allocator.enable_reclaim default based on build 
instructions
  TS-1006: adjust some reclaimable-freelist's default configuration
  Updated newish tests to the gitignore
  Fix autoconf checks for mcheck_pedantic()
  Fix configure check for eventfd
  TS-1330: Fix logging core at checkout_write()
  add some standard extensions to ignore list
  TS-1953: remove version check from stable plugins
  TS-1953: Remove check_ts_version() from experimental plugins
  TS-1953: remove check_ts_version() from examples
  Added TS-2086.
  TS-2086 Remove a few more unused configs
  Added TS-1685
  TS-1685 Remove TS_MICRO and fellas
  Added Ts-1255
  TS-1255 Fix the types for all overridable configs. This was actually a real 
bug in the code, in that all float configurations were actually treated as 
integer, rendering them useless
  ...

                
> Add more overridable records.config configurations
> --------------------------------------------------
>
>                 Key: TS-1255
>                 URL: https://issues.apache.org/jira/browse/TS-1255
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: TS API
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>              Labels: A
>             Fix For: 3.3.5
>
>
> We should examine at least the following configs, and see which ones can (or 
> can not) be moved to be overridable:
> {code}
>   MgmtInt server_max_connections;
>   MgmtInt origin_min_keep_alive_connections; // TODO: This one really ought 
> to be overridable, but difficult right now.
>   char *proxy_request_via_string;
>   int proxy_request_via_string_len;
>   char *proxy_response_via_string;
>   int proxy_response_via_string_len;
>   MgmtInt origin_server_pipeline;
>   MgmtInt user_agent_pipeline;
>   MgmtInt transaction_active_timeout_in;
>   MgmtInt accept_no_activity_timeout;
>   MgmtInt background_fill_active_timeout;
>   MgmtFloat background_fill_threshold;
>   MgmtInt parent_connect_attempts;
>   MgmtInt per_parent_connect_attempts;
>   MgmtInt parent_connect_timeout;
>   MgmtByte insert_age_in_response;
>   MgmtByte avoid_content_spoofing;
>   MgmtByte enable_http_stats;
>   MgmtInt max_cache_open_write_retries;
>   MgmtByte cache_enable_default_vary_headers;
>   MgmtByte cache_when_to_add_no_cache_to_msie_requests;
>   MgmtByte cache_range_lookup;
>   MgmtInt request_hdr_max_size;
>   MgmtInt response_hdr_max_size;
>   MgmtByte push_method_enabled;
>   MgmtByte referer_filter_enabled;
>   MgmtByte referer_format_redirect;
>   MgmtByte accept_encoding_filter_enabled;
>   // WTF!!! Bool ???
>   /// Accept connections on foreign addresses.
>   bool client_transparency_enabled;
>   /// Use client address to connect to origin server.
>   bool server_transparency_enabled;
>   MgmtByte negative_revalidating_enabled;
>   MgmtInt negative_revalidating_lifetime;
>   MgmtByte ignore_accept_mismatch;
>   MgmtByte ignore_accept_language_mismatch;
>   MgmtByte ignore_accept_encoding_mismatch;
>   MgmtByte ignore_accept_charset_mismatch;
>   ////////////////////////////////
>   // Optimize gzip alternates   //
>   ////////////////////////////////
>   MgmtByte normalize_ae_gzip;
> {code}
> Marking this for v3.3.0, it'd be nice to get into 3.2, but I rather have us 
> just get 3.1.4/3.2 done sooner rather than later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to