-
Notifications
You must be signed in to change notification settings - Fork 37
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
Permission denied when running the test #53
Comments
Maybe you don't have permission to listen on that port? What is the code you're testing? |
It's a node.js server that's working fine (I'm actually testing it with Objective-C and Chrome's Dev HTTP Client utility. I'm running on port 8080 without issues:
Assuming that the server is running fine, the above code would report a 403 as opposed to permission denied, right? Or is this permission denied the result of an HTTP 403? (which the server returns if no authentication has succeeded) Thank you. |
I'm having no trouble at all performing the invocation from the browser. Weird... |
OK, somehow I got it to work (I've tried so many things I'm not sure what made it work.) This is the dummy test I setup in place:
This is the test:
When I call npm test, I get the following:
How in the world is it getting a 400? It's impossible! Again, if I invoke it via http://localhost:8080/admin/stats I get back:
Even Charles proxy shows that the response is a 200. What gives? |
Hi,
I've tried to follow the instructions, but I keep on getting a "Permission denied" error:
I'm not sure what's wrong. This is what tests/connect-test.js looks like:
The permissions look like this
Any ideas? Thanks!
The text was updated successfully, but these errors were encountered: