Closed mik01aj closed 9 years ago
I think the problem in #22 is a missing baseUri definition in the RAML. Could this also be your case?
Anyways, 0.0.4 is a very old release. I'm going to release a new one based on raml-tester 0.8.2 which fixes the baseUri problem and logs any occurring problems.
Ok, there's a new version 0.8.3, can you try with it?
Looks like fixed. I get responses from the proxy and I see the logs in the console. Thanks.
This looks related to https://github.com/nidi3/raml-tester-proxy/issues/22.
The problem is, as I saw in the above issue that
file://
urls are problematic, I usedpython -m SimpleHTTPServer
to start a local server. Then I started the proxy with this server, and it loaded the RAML definitions (I saw that it reqeuested theinclude
d files), but it's still neither answering any requests nor producing any log output. It just created an empty directory for the logs, nothing more.Here's the full command line and output (note that these lines starting with
127.0.0.1
come from the Python server, not theraml-proxy
):I'm using version
0.0.4
from npm (https://github.com/nidi3/raml-tester-js).