Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[upstream] support path in the upstream url #905

Merged
merged 1 commit into from
Sep 26, 2018
Merged

Conversation

mikz
Copy link
Contributor

@mikz mikz commented Sep 19, 2018

Route traffic to that path + current url.

Closes #903

@mikz mikz requested a review from a team as a code owner September 19, 2018 16:11
@mikz mikz force-pushed the upstream-path-spec branch 3 times, most recently from 30df666 to 8967e37 Compare September 25, 2018 14:00
Route traffic to that path + current url.
@mikz mikz force-pushed the upstream-path-spec branch from 8967e37 to fe6faad Compare September 26, 2018 08:53
}
--- request
GET /some_path?user_key=uk&a_param=a_value
--- response_body
yay, api backend
GET /path_in_the_rule/some_path?user_key=uk&a_param=a_value HTTP/1.1
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically this is a breaking change as it used to be GET /path_in_the_rule.

But I was thinking that the upstream policy needs some improvements anyway. For example, stripping the path that it matched from the URL etc. So we can make general improvements to that policy and make it configurable how it operates on URI paths.

@davidor davidor merged commit 4442dc9 into master Sep 26, 2018
@davidor davidor deleted the upstream-path-spec branch September 26, 2018 10:54
@davidor davidor added this to the 3.4 milestone Oct 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants