The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Curl access to alternate port

I am having difficulty using CURL to access a remote server on a non-standard port. I am new to this forum and until I have 1o posts, I cannot post urls, so the following urls have the word 'slash''slash' substitued.

Example: The url (http:'slash'slash'socket.carfax.com:8080) should should return the following: "901 Transaction Error". Type it into a browser address window and it returns the desired result.

The following php script attempts to do the same via CURL, three different ways. All return the same result....nothing....

RE Enabling Curl. Curl is enabled, and I use it okay for other functionality. This problem is occurring due to my need to send to a specific port on the remote server.

RE port blocking by Godaddy. I'm do not know a lot in this area, so my question is this:

I am sending a request to a 3rd party server specifying port 8080. I thought that meant that the 3rd party server will receive it on port 8080. Does it also mean that I am sending it out through port 8080 on my server?

I am sending a request to a 3rd party server specifying port 8080. I thought that meant that the 3rd party server will receive it on port 8080. Does it also mean that I am sending it out through port 8080 on my server?

No, you right. It means the destination address receives the request on port 8080.

The problem is that Godaddy shared hosting will not let you make requests from your site that go to any port other than 80.

It's like having a house where all of the doors and windows, except the front door, are welded shut.

You'll have to contact Godaddy support and ask them if the dedicated packages have the same restrictions on ports as shared packages have, I don't know if they do.

Resolved - Talked to Godaddy Support and was told port 8080 is blocked, even on their dedicated servers. (I was told I had complete control of my leased server when I signed up...guess that isn't quite so).