docs: add 2.1.0 breaking-change note for listener port matching#2784
Open
AlinsRan wants to merge 1 commit into
Open
docs: add 2.1.0 breaking-change note for listener port matching#2784AlinsRan wants to merge 1 commit into
AlinsRan wants to merge 1 commit into
Conversation
AlinsRan
force-pushed
the
fix/listener-port-match-default-off
branch
3 times, most recently
from
ff2e73b to
c300ecb
Compare
AlinsRan
changed the title
Port-based routing (apache#2703) injects a server_port var from the Gateway listener port, but APISIX server_port reflects the data-plane listening port (e.g. 9080/9443). When they differ, routes 404. Document this in the 2.1.0 CHANGELOG with the listener_port_match_mode: off mitigation.
AlinsRan
force-pushed
the
fix/listener-port-match-default-off
branch
from
c300ecb to
7bbe58e
Compare
AlinsRan
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What this PR does
Adds a Breaking Changes note to the 2.1.0 CHANGELOG documenting the
server_port/ listener-port-match behavior. CHANGELOG only — no code or default change.Why
Port-based routing for Gateway API routes (#2703, shipped in 2.1.0) injects a
server_portroute var derived from the Gateway listener port (e.g.80/443). But the APISIXserver_portvariable reflects the port the data plane actually listens on (e.g.9080/9443, when a Service maps80/443 → 9080/9443). When those differ, the injected var never matches and routes return404after upgrading.The note explains what changed, why it can break, and the
listener_port_match_mode: offmitigation. See #2782.Refs #2782