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

Extra slash after hostname during api request returns 405 error (unless using partialName) #6964

Closed
6 tasks done
AdamHollow49 opened this issue Jul 29, 2021 · 2 comments
Closed
6 tasks done
Assignees
Labels
area/core kind/bug This issue represents a verified problem we are committed to solving tag/regression This issue was addressed and shipped, but subsequently broken in another release

Comments

@AdamHollow49
Copy link

AdamHollow49 commented Jul 29, 2021

Prerequisites

  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have labeled the value stream (area/core, area/steps, ...)
  • I have tagged the issue appropriately (kind/bug, kind/enhancement, feature/ ...)

The bug

When querying the API for specific data, including an extra slash after the server hostname returns a 405 error.

What I expected to happen

The request should be resolved successfully.

Steps to reproduce

  1. Make a request to the API of an Octopus Server for a specific resource:
    'https://octopus-server/api/Spaces-1/projects/Project-1'

  2. Add an extra slash after the hostname of the server:
    'https://octopus-server//api/Spaces-1/projects/Project-1'

Screen capture

image

Affected versions

Octopus Server: 2021.1.7595
Issue was not present in 2021.1.7500

Workarounds

If the name of the resource is known, you can use partialName=NAME to have the request succeed however this may cause different issues.

Links

Internal User Issue with investigation: https://octopus.zendesk.com/agent/tickets/72854

@AdamHollow49 AdamHollow49 added kind/bug This issue represents a verified problem we are committed to solving tag/regression This issue was addressed and shipped, but subsequently broken in another release area/core labels Jul 29, 2021
@tothegills
Copy link
Contributor

@Octobob
Copy link
Member

Octobob commented Jan 18, 2022

🎉 The fix for this issue has been released in:

Release stream Release
2021.1 2021.1.7660
2021.2 2021.2.7154
2021.3 2021.3.1254
2022.1+ all releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core kind/bug This issue represents a verified problem we are committed to solving tag/regression This issue was addressed and shipped, but subsequently broken in another release
Projects
None yet
Development

No branches or pull requests

4 participants