-
Notifications
You must be signed in to change notification settings - Fork 237
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
Uncaught URIError: URI malformed #528
Comments
Hi, |
@adamserafini Is it possible for you to send me an example response that throws this error? |
Hi @jarrodek I don't think there is a problem in the response because if I use a known 'correct' API the same things happens. For example check response here and screenshot below: https://jsonplaceholder.typicode.com/posts Also what is weird - In the network tab it never makes a call to the URL https://jsonplaceholder.typicode.com/posts - is that expected? It is like something is going wrong before the requests even gets made. |
This is now fixed in 6.0.0 as it has different approach to parsing response. |
I have the following raml file which I build using
api-console build --json api.raml
I then copy the files the contents of /build folder to an ngnix server at http://mydocserver.com
The problem is at the point when I want to 'TRY' the api from the page hosted on the doc server. I get a message like in the following screenshot:
Any pointers where I'm going wrong?
The text was updated successfully, but these errors were encountered: