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

I post JSON in private network ip and other port like 192.168.x.x:1234 or localhost:1234 #133

Closed
ivanchiou opened this Issue Sep 5, 2014 · 7 comments

Comments

Projects
None yet
5 participants
@ivanchiou

ivanchiou commented Sep 5, 2014

HI,
I post JSON to server in private network its ip and port like http://192.168.x.x:1234 or http://localhost:1234. The server return http status code 500 and get everythings except request content(JSON body) so I can't recognize what data the client sent to server. Otherwise server in public ip, it works normally. Is some settings I miss in this case? Please help me to check below errors.

Frisby Test: xxxxxxxxxxxxxxxxxxxxxx
[ POST http://xxx:xxxxxxxxxxxxx@localhost:1234/api/ ]
Message:
Expected 500 to equal 201.
Stacktrace:
Error: Expected 500 to equal 201.
at null. (/usr/lib/node_modules/frisby/lib/frisby.js:485:42)
at null. (/usr/lib/node_modules/frisby/lib/frisby.js:1066:43)
at Timer.listOnTimeout as ontimeout

@ivanchiou

This comment has been minimized.

Show comment
Hide comment
@ivanchiou

ivanchiou Oct 16, 2014

I also met the same problem. Did some one know the answer or this is just a limitation on frisby? How to solve it? It has bottled me a long time... Thanks.

ivanchiou commented Oct 16, 2014

I also met the same problem. Did some one know the answer or this is just a limitation on frisby? How to solve it? It has bottled me a long time... Thanks.

@vlucas

This comment has been minimized.

Show comment
Hide comment
@vlucas

vlucas Oct 16, 2014

Owner

If the request is returning a status code, it is not failing. What is the body content returned? Can you check with .inspectBody()?

Owner

vlucas commented Oct 16, 2014

If the request is returning a status code, it is not failing. What is the body content returned? Can you check with .inspectBody()?

@amgray789

This comment has been minimized.

Show comment
Hide comment
@amgray789

amgray789 Oct 23, 2014

I too get the same error. The .inspectBody() produces the following

"Destination URL may be down or URL is invalid."

amgray789 commented Oct 23, 2014

I too get the same error. The .inspectBody() produces the following

"Destination URL may be down or URL is invalid."

@amgray789

This comment has been minimized.

Show comment
Hide comment
@amgray789

amgray789 Oct 23, 2014

Further investigation revealed this

process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0';

nodejs/node-v0.x-archive#4023

amgray789 commented Oct 23, 2014

Further investigation revealed this

process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0';

nodejs/node-v0.x-archive#4023

@repat repat referenced this issue Jan 26, 2015

Open

Test locally #1

@comscience15

This comment has been minimized.

Show comment
Hide comment
@comscience15

comscience15 Jul 17, 2015

I too get the same error. The .inspectBody() produces the following

"Destination URL may be down or URL is invalid."

^ I got the same thing. So what is the solution for this. I think I need to change the port number from standard(8080) to be (8090). How to do it on Frisby???

comscience15 commented Jul 17, 2015

I too get the same error. The .inspectBody() produces the following

"Destination URL may be down or URL is invalid."

^ I got the same thing. So what is the solution for this. I think I need to change the port number from standard(8080) to be (8090). How to do it on Frisby???

@rdohms

This comment has been minimized.

Show comment
Hide comment
@rdohms

rdohms Nov 25, 2016

I'm getting this as well, what was the fix?

rdohms commented Nov 25, 2016

I'm getting this as well, what was the fix?

@vlucas

This comment has been minimized.

Show comment
Hide comment
@vlucas

vlucas Jul 26, 2017

Owner

Looks like it was a bad SSL cert. Can you try this with v2 and then re-open this issue if it still doesn't work? The fetch() API should be able to handle this.

Owner

vlucas commented Jul 26, 2017

Looks like it was a bad SSL cert. Can you try this with v2 and then re-open this issue if it still doesn't work? The fetch() API should be able to handle this.

@vlucas vlucas closed this Jul 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment