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

Load balanced URIs get mangled in DefaultLinkResolver.Resolve #455

Open
ryanrousseau opened this issue Aug 26, 2019 · 0 comments
Open

Load balanced URIs get mangled in DefaultLinkResolver.Resolve #455

ryanrousseau opened this issue Aug 26, 2019 · 0 comments

Comments

@ryanrousseau
Copy link
Contributor

When using a load balanced URI with OctopusClient, the response.Location from DispacthRequest can be a fully qualified URI. This is passed to DefaultLinkResolver which sees that it does not begin with a / and adds a / to the beginning of the fully qualified URI.

This can be reproduced by using octo.exe create-release using a load balanced URI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant