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

API path is incorrect under prefix #2247

Closed
errordeveloper opened this issue Feb 15, 2017 · 4 comments
Closed

API path is incorrect under prefix #2247

errordeveloper opened this issue Feb 15, 2017 · 4 comments
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@errordeveloper
Copy link
Contributor

errordeveloper commented Feb 15, 2017

I'm trying to update DC/OS package for Scope to use version 1.2.0.

Once installed the package on DC/OS, I need to go to https://<dcos_host>/service/weavescope, and the UI loads okay, but it tries to access the API on a weird URL.

The URL it tries to call is https://<dcos_host>/api/service/weavescope/api/topology, while it should be /service/weavescope/api/topology.

If I load /service/weavescope/api/topology, I can see the topology, while /api/service/weavescope/api/topology gives me a 404, as DC/OS doesn't have a route for it.

How does this /api get prepended? I'm looking at getApiPath() in client/app/scripts/utils/web-api-utils.js, is it the right place to look or not?

@errordeveloper
Copy link
Contributor Author

errordeveloper commented Feb 15, 2017

I've tested 1.1.0, and can see the same issue with it.

(After a while, perhaps 1 hour, 1.1.0 started working, so I assume the above statement was false and it's probably to do with cache).

@jpellizzari jpellizzari self-assigned this Feb 15, 2017
@jpellizzari
Copy link
Contributor

This was fixed in #2202, but that PR was not merged until after the release.

@jpellizzari jpellizzari mentioned this issue Feb 15, 2017
6 tasks
@2opremio 2opremio added the bug Broken end user or developer functionality; not working as the developers intended it label Feb 15, 2017
@2opremio
Copy link
Contributor

Duplicate of #2154

@2opremio 2opremio added this to the n/a milestone Feb 15, 2017
@2opremio
Copy link
Contributor

The fix will be released in 1.2.1, coming out imminently (#2250 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

3 participants