Hello,

When I try to verify links on the system, the links all end in :80 and they are all bad to the system.

How do I solve this problem?

Thanks in advance.

James L. Murray
VirtueTech, Inc.
www.virtuetech.com

James,

The :80 should not be causing the verification to fail. The 80 is the default port number that almost all web servers run under. It can be appended to the end of a URL with no adverse affect unless the destination server runs under a different port.

For example, if you wanted to go to the Gossamer Threads home page, you could specify the URL one of two ways:

http://www.gossamer-threads.com

or

http://www.gossamer-threads.com:80

Both work equally well. So, if the verification process is failing, it is not the port number causing it. What are the error/status messages you are receiving back for each link?

[This message has been edited by Bobsie (edited June 09, 1999).]

Hello,

It says the following:

Can't connect to www.randolphpaintball.com:80

Maybe it's because it is not using the http:// protocol in front of the url.

If that is so, how do I make it do that.

Thanks in advance.

Every "Can't Connect" message I get has a reason following it in parenthesis. There is nothing like that in your error messages?

Don't confuse the error message with what is actually being done. When nph-verify.cgi attempts to verify the link, it does use the correct protocol. The error message just doesn't show it.

Is it happening with every link you have or just some of them?

Hello,

It verify's 2 links out of 50.

The links do not have any chronological order to them. Is that normal?

Here is the actual lines of the Errors:

Links to check '25' using GET method. Please be patient...

Checked 8 - Request Failed (500). Message: Can't connect to www.warpig.com:80 (Connection refused).
Checked 26 - Request Failed (500). Message: Can't connect to www.paintsplat.com:80 (Connection refused).
Checked 28 - Request Failed (500). Message: Can't connect to order.outinstyle.com:80 (Connection refused).
Checked 30 - Request Failed (500). Message: Can't connect to www.funsupply.com:80 (Connection refused).
Checked 24 - Request Failed (500). Message: Can't connect to www.californiapaintball.com:80 (Connection refused).
Checked 31 - Request Failed (500). Message: Can't connect to www.bullseyepaintball.com:80 (Connection refused).
Checked 32 - Request Failed (500). Message: Can't connect to www.worr.com:80 (Connection refused).
Checked 34 - Request Failed (500). Message: Can't connect to www.randolphpaintball.com:80 (Connection refused).
Checked 36 - Request Failed (500). Message: Can't connect to www.erols.com:80 (Connection refused).
Checked 39 - Request Failed (500). Message: Can't connect to www.expage.com:80 (Connection refused).
Checked 40 - Request Failed (500). Message: Can't connect to www.legendlogbooks.com:80 (Connection refused).
Checked 41 - Request Failed (500). Message: Can't connect to mikespaintball.com:80 (Connection refused).
Checked 43 - Request Failed (500). Message: Can't connect to wolvpb.com:80 (Connection refused).
Checked 44 - Request Failed (500). Message: Can't connect to www.paintballsportsinc.com:80 (Connection refused).
Checked 45 - Request Failed (500). Message: Can't connect to www.rockhillbiz.com:80 (Connection refused).
Checked 46 - Request Failed (500). Message: Can't connect to www.splatmasters.com:80 (Connection refused).
Checked 48 - Request Failed (500). Message: Can't connect to members.tripod.com:80 (Connection refused).
Checked 49 - Request Failed (500). Message: Can't connect to paintballunlimited.com:80 (Connection refused).
Checked 50 - Request Failed (500). Message: Can't connect to teamadrenalin.com:80 (Connection refused).
Checked 51 - Request Failed (500). Message: Can't connect to www.jtusa.com:80 (Connection refused).
Checked 52 - Request Failed (500). Message: Can't connect to teamkamikaze.webjump.com:80 (Connection refused).
Checked 53 - Request Failed (500). Message: Can't connect to www.timberwolvespaintball.com:80 (Connection refused).
Checked 54 - Request Failed (500). Message: Can't connect to www.paintballandmore.com:80 (Connection refused).
Checked 22 - Success (200). Message: OK. URL: http://www.teamgroundzero.com/
Checked 6 - Success (200). Message: OK. URL: http://www.playpaintball.com/

Took: 1 seconds to check 25 links.

James

GZ pointed out a possible problem and your output verifies it. The URLS that result in a "Cannot connect..." error message are incomplete. They are missing the http:// portion. You'll need to edit all the records and add http:// where missing - 48 out of the 50.

Then you should be able to verify the links without incident. BTW, how is that the http:// is missing? For the input text box you should add value="http://".

Dan

Dan,

As I pointed out in an earlier message, the "http://" part is not shown in the error messages that are returned, just the domain is shown, so the messages really do not confirm that those records have it missing. However, it wouldn't hurt to check the records.

Ground Zero,

Yes, it is normal for the records to be returned in non-chronological order. Although Links sends out a request for the validation in chronological order, the replies it receives back may not be that way due to time delays experienced on the internet route or on the destination servers themselves.

The fact that two records did get validated indicates to me that nph-verify is working correctly. Therefore, as Dan has said, something is wrong in those records. You might want to take a close look at the ones that failed. Either that, or your server is being blocked somehow on the destination servers (not very likely though).

Thanks guys.

I'm going to try to manually get the http:// protocol infront of the domain.

I think

James