Merging to release-5.3.5: [TT-13087] Adjust example gateway config, to have match preficing explicit by default (#6564) #6571
Conversation
This file contains 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
…licit by default (#6564) ### **User description** ## Description TT-13087 Adjust example gateway config, to have match preficing explicit by default ## Motivation and Context Would be advised that Gateway users, would have by default explicit path matching settings enabled by default, as the wildcard behaviour of the path matching, can be challenging at times to configure properly. ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [x] Breaking change (fix or feature that would cause existing functionality to change) - [x] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [x] I ensured that the documentation is up to date - [x] I explained why this PR updates go.mod in detail with reasoning why it's required - [x] I would like a code coverage CI quality gate exception and have explained why ___ ### **PR Type** enhancement, configuration changes ___ ### **Description** - Added new configuration options in `tyk.conf.example` to enable strict routing and explicit path matching by default. - The changes aim to improve the default behavior for gateway users by making path matching settings explicit. ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Configuration changes</strong></td><td><table> <tr> <td> <details> <summary><strong>tyk.conf.example</strong><dd><code>Add explicit path matching options to example gateway config</code></dd></summary> <hr> tyk.conf.example <li>Added <code>http_server_options</code> section.<br> <li> Enabled <code>enable_strict_routes</code>.<br> <li> Enabled <code>enable_path_prefix_matching</code>.<br> <li> Enabled <code>enable_path_suffix_matching</code>. </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6564/files#diff-a6736b4b3cda1ee503675d7b725f6138f4eb83d7145f3afecf6087d219f2b23a">+5/-0</a> </td> </tr> </table></td></tr></tr></tbody></table> ___ > 💡 **PR-Agent usage**: Comment `/help "your question"` on any pull request to receive relevant information (cherry picked from commit d98cc03)
|
API Changes no api changes detected |
PR Reviewer Guide 🔍
|
PR Code Suggestions ✨
|
|
lghiur
deleted the
merge/release-5.3.5/d98cc036e3d7afde6d9292d42520b301481dc5f3
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
User description
TT-13087 Adjust example gateway config, to have match preficing explicit by default (#6564)
User description
Description
TT-13087 Adjust example gateway config, to have match preficing explicit
by default
Motivation and Context
Would be advised that Gateway users, would have by default explicit path
matching settings enabled by default, as the wildcard behaviour of the
path matching, can be challenging at times to configure properly.
How This Has Been Tested
Types of changes
functionality to change)
coverage to functionality)
Checklist
why it's required
explained why
PR Type
enhancement, configuration changes
Description
tyk.conf.exampleto enable strictrouting and explicit path matching by default.
making path matching settings explicit.
Changes walkthrough 📝
tyk.conf.example
Add explicit path matching options to example gateway configtyk.conf.example
http_server_optionssection.enable_strict_routes.enable_path_prefix_matching.enable_path_suffix_matching.PR Type
enhancement, configuration changes
Description
tyk.conf.exampleto enable strict routing and explicit path matching by default.http_server_optionswithenable_strict_routes,enable_path_prefix_matching, andenable_path_suffix_matchingset to true.Changes walkthrough 📝
tyk.conf.example
Add explicit path matching options to example gateway configtyk.conf.example
http_server_optionssection.enable_strict_routes.enable_path_prefix_matching.enable_path_suffix_matching.