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

fix: Fix url resolving in the bitbucket api client #346

Merged
merged 1 commit into from
Aug 30, 2022
Merged

Conversation

vinokurig
Copy link
Contributor

@vinokurig vinokurig commented Aug 30, 2022

Signed-off-by: Igor Vinokur ivinokur@redhat.com

What does this PR do?

Fix a bug where url is not resolved correctly if a server url has path segments. URI.create(https://server-url/path-segment).resolve(/second-path) returns https://server-url/second-path, so the path-segment is ignored. See for more details.

Add a trailing / to the server url and make the rest api segments reletive to fix the problem.

Screenshot/screencast of this PR

What issues does this PR fix or reference?

How to test this PR?

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Signed-off-by: Igor Vinokur <ivinokur@redhat.com>
@vinokurig vinokurig merged commit 86799d5 into main Aug 30, 2022
@vinokurig vinokurig deleted the che-21189 branch August 30, 2022 11:53
@che-bot che-bot added this to the 7.53 milestone Aug 30, 2022
vinokurig added a commit that referenced this pull request Aug 30, 2022
Fix a bug where url is not resolved correctly if a server url has path segments. URI.create(https://server-url/path-segment).resolve(/second-path) returns https://server-url/second-path, so the path-segment is ignored. See for more details.

Add a trailing / to the server url and make the rest api segments reletive to fix the problem.
@ibuziuk ibuziuk mentioned this pull request Aug 30, 2022
82 tasks
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.

3 participants