Level 5
You should use something like Postman to test this kinda stuff.
Mar 1, 2018
3
Level 1
other port other than 80 and Guzzle do not get along?
I have a server in my local network where I have a webservice made in Laravel that uses Guzzle 6.3. Said webservice is consumed by a web that is outside of my local area network, in a hosting provider. I have a router where I configured an external 7844 port and it is redirected to the internal port 80 of my webservice server. When making requests from the external hosting, the connection is rejected. When I use port 80 or 8080 to connect from the hosting to the webservice. . .then if he walks. Guzzle has a problem with ports other than 80 or 8080? I found something to hear about the Guzzle theme in version 6.3 regarding 5.
Thanks for your attention
Level 1
I already tried postman, eventually it works it eventually fails. For example, I consulted the same API from Postman with port 7744 and it answered correctly, and at the same time that API consulted it from a website and did not answer. I would really like to know if this is a configuration problem of port forwarding or a problem in the Guzzle library.
Thank you!
Level 5
Can you paste the piece of code that is making this api call? Also make sure there is no firewall in between if you tried Postman on a different server than your webapp.
Please or to participate in this conversation.