proxy.config.ssl.session_cache.mode #12414
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bneradt
force-pushed
the
fix_session_server_cache_config
branch
from
68a6345 to
5368a96
Compare
bneradt
force-pushed
the
fix_session_server_cache_config
branch
2 times, most recently
from
78b8ff8 to
8ce35de
Compare
In the 10.0.0 release, we renamed proxy.config.ssl.session_cache.enabled to proxy.config.ssl.session_cache.value because enabled seemed incorrect for a configuration that took a non-boolean enumeration of values. We accidentially left the documentation describing proxy.config.ssl.session_cache.enabled, however. In discussion about this, we decided to rename such configurations to "mode" instead of value. Another issue (apache#12412) records making these renames for 11.0.0. This PR just addresses the current issues with proxy.config.ssl.session_cache.enabled by: * Adding implementation support for proxy.config.ssl.session_cache.enabled since we documented that already but document it as deprecated. * Keep implementation support for proxy.config.ssl.session_cache.value since users might be using that. * Add proxy.config.ssl.session_cache.mode as the preferred new mode. The user can set values for any of these via: * implicit default config values, * plugin default values via TSMgmtIntCreate, * explicit records.yaml values, or * override via environment variable. It will probably be a very rare user that implements any of these across values, but in case they do, this patch implements a selection of the finally chosen config value based on a priority base of the above, with "mode" valued over "value" valued over "enabled". Fixes: 11901
bneradt
force-pushed
the
fix_session_server_cache_config
branch
from
8ce35de to
60911a5
Compare
maskit
approved these changes
Aug 4, 2025
ezelkow1
approved these changes
Aug 4, 2025
bneradt
added a commit
to bneradt/trafficserver
that referenced
this pull request
Aug 4, 2025
In the 10.0.0 release, we renamed proxy.config.ssl.session_cache.enabled to proxy.config.ssl.session_cache.value because enabled seemed incorrect for a configuration that took a non-boolean enumeration of values. We accidentially left the documentation describing proxy.config.ssl.session_cache.enabled, however. In discussion about this, we decided to rename such configurations to "mode" instead of value. Another issue (apache#12412) records making these renames for 11.0.0. This PR just addresses the current issues with proxy.config.ssl.session_cache.enabled by: * Adding implementation support for proxy.config.ssl.session_cache.enabled since we documented that already but document it as deprecated. * Keep implementation support for proxy.config.ssl.session_cache.value since users might be using that. * Add proxy.config.ssl.session_cache.mode as the preferred new mode. The user can set values for any of these via: * implicit default config values, * plugin default values via TSMgmtIntCreate, * explicit records.yaml values, or * override via environment variable. It will probably be a very rare user that implements any of these across values, but in case they do, this patch implements a selection of the finally chosen config value based on a priority base of the above, with "mode" valued over "value" valued over "enabled". Fixes: apache#11901 (cherry picked from commit 87bb602)
cmcfarlen
pushed a commit
that referenced
this pull request
Aug 5, 2025
In the 10.0.0 release, we renamed proxy.config.ssl.session_cache.enabled to proxy.config.ssl.session_cache.value because enabled seemed incorrect for a configuration that took a non-boolean enumeration of values. We accidentially left the documentation describing proxy.config.ssl.session_cache.enabled, however. In discussion about this, we decided to rename such configurations to "mode" instead of value. Another issue (#12412) records making these renames for 11.0.0. This PR just addresses the current issues with proxy.config.ssl.session_cache.enabled by: * Adding implementation support for proxy.config.ssl.session_cache.enabled since we documented that already but document it as deprecated. * Keep implementation support for proxy.config.ssl.session_cache.value since users might be using that. * Add proxy.config.ssl.session_cache.mode as the preferred new mode. The user can set values for any of these via: * implicit default config values, * plugin default values via TSMgmtIntCreate, * explicit records.yaml values, or * override via environment variable. It will probably be a very rare user that implements any of these across values, but in case they do, this patch implements a selection of the finally chosen config value based on a priority base of the above, with "mode" valued over "value" valued over "enabled". Fixes: #11901 (cherry picked from commit 87bb602)
Contributor
|
Milestone 10.1.0 via #12419 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the 10.0.0 release, we renamed proxy.config.ssl.session_cache.enabled to proxy.config.ssl.session_cache.value because enabled seemed incorrect for a configuration that took a non-boolean enumeration of values. We accidentially left the documentation describing
proxy.config.ssl.session_cache.enabled, however. In discussion about this, we decided to rename such configurations to "mode" instead of value. Another issue (#12412) records making these renames for 11.0.0. This PR just addresses the current issues with
proxy.config.ssl.session_cache.enabled by:
The user can set values for any of these via:
It will probably be a very rare user that implements any of these across values, but in case they do, this patch implements a selection of the finally chosen config value based on a priority base of the above, with "mode" valued over "value" valued over "enabled".
Fixes: #11901