Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Move Roxy off Query Console endpoint #612

Closed
clockworked247 opened this issue May 17, 2016 · 2 comments
Closed

Move Roxy off Query Console endpoint #612

clockworked247 opened this issue May 17, 2016 · 2 comments
Assignees
Milestone

Comments

@clockworked247
Copy link

clockworked247 commented May 17, 2016

Roxy should be using the /v1/eval endpoint instead. ML 9 will add deeper security to QC endpoints, no longer allowing for Roxy or any other unauthorized requestors to use them.

@dmcassel
Copy link
Collaborator

+1 on this. We can probably do it for ML8 as well, since that's when the endpoint became available.

@dmcassel dmcassel added this to the 1.7.4 milestone May 18, 2016
@dmcassel dmcassel self-assigned this May 18, 2016
dmcassel added a commit to dmcassel/roxy that referenced this issue May 19, 2016
dmcassel added a commit to dmcassel/roxy that referenced this issue Jul 8, 2016
dmcassel added a commit to dmcassel/roxy that referenced this issue Jul 8, 2016
@grtjn
Copy link
Contributor

grtjn commented Jul 12, 2016

Fixed in dev..

@grtjn grtjn closed this as completed Jul 12, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants