Keep getting 404 in API Designer about api-console HOT 3 CLOSED

I read more about proxies at API Console|Configuring.The doc was a bit cryptic:

A proxy for Try It can be provided after loading the console
JavaScript. For example:

RAML.Settings.proxy = 'http://www.someproxy.com/somepath/' Given the
above, trying a GET to http://www.someapi.com/resource would get

http://www.someproxy.com/somepath/http://www.someapi.com/resource

I eventually found where this was set, in dist/index.html, near the bottom.
Since I don't have a proxy, I just updated this to

 RAML.Settings.proxy = '';

and now my API Console can call my REST service.

The documentation should be updated, and I suggest also updating the default distribution to not set a proxy, so that API Console works for initial development of an API on the same host, or that it detects errors due to an incorrectly configured proxy (i.e. if RAML.Settings.proxy is still set to '/proxy/' )

from api-console.

Any updates on this? See my comment on the above forum thread. I get 404 even when I'm running the API and API Console on the same server. Currently, this is a major blocker

from api-console.

I had this problem in the Mulesoft API Manager service mocking feature as well recently. Turning mocking on and off solved my problem and it works fine now (but the endpoint has been changed).

from api-console.