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

Unable to connect API to a proxy in nightly APInf #3228

Closed
Nazarah opened this issue Dec 13, 2017 · 3 comments
Closed

Unable to connect API to a proxy in nightly APInf #3228

Nazarah opened this issue Dec 13, 2017 · 3 comments
Assignees
Labels

Comments

@Nazarah
Copy link
Contributor

Nazarah commented Dec 13, 2017

Steps to Reproduce:

  1. go to page: https://nightly.apinf.io and login
  2. Click Add API and start adding an API manually (used the following endpoint URL: https://nightly.apinf.io)
  3. After adding the API, go to proxy tab in API profile.
  4. Select Nightly Umbrella as proxy and add '/v/' as proxy base path and '/ ' as API base path.
  5. Click Save and publish

Outcome:
Proxy set up doesn't get saved.
s-alert shows error: "can't read property length of null value".
If tried to change the selected proxy, the proxy name didn't change in the respected field.
If tried to save and publish by changing the proxy, it failed.
S alert showed error: failed [500] {"status"."500","error","Internal Server Error"}
http://recordit.co/lbmjMT5RwW

Expected Behavior:

added values for proxy base path and api base path should be saved accordingly.
User should be able to see Get API Key button upon publishinbg.

Environment:

Windows 10, Chrome browser (latest), APInf nightly (https://nightly.apinf.io)

@Nazarah Nazarah added the bug label Dec 13, 2017
@Nazarah
Copy link
Contributor Author

Nazarah commented Dec 13, 2017

behavior in staging platform.
Added an API with endpoint: https://staging.aping.io.
tried to connect it to Nihgtly Umbrella proxy with the /v1/ proxy base path and / api base path.
Got the error "can't read property 'length' of null."
tried to change the proxy to api-umbrella 1 and save
got the same error.
Again changed back to nightly umbrella proxy and clicked save.
This time was able to save and publish the API.
http://recordit.co/0skuM9RUVR

@preriasusi
Copy link
Contributor

Nigthly's proxy seems to give this error. Devops?

@anarva
Copy link
Contributor

anarva commented Feb 8, 2018

Tested and working now fine. Resolved by cumulated changes. Can be closed.

@anarva anarva closed this as completed Feb 8, 2018
@ghost ghost removed the ready label Feb 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants