Jump to ContentJump to Navigation/Login
` ` ` ` ` `

[Register]

Occasional ATutor release updates


No Members Logged In

(3 guests in past 15 min.)

Access Understanding Web Accessibility to learn about accessibility, or Register to take the course for FREE.

Support Forums

AChecker

"cannot connect to URL" errors


You must be signed-in to post.

AuthorSubject
  Page: 1
andrewec
Subject: "cannot connect to URL" errorsQuote this post in your reply
Hi,

On some sites achecker works great checking the accessibility against guidelines wcag 1.0 aaa and 2.0 aaa but some sites give "cannot connect to URL" errors, even if no wcag guidelines are set. Please advise how to fix this issue.

Thanks,
Andrew

Things to describe:

Operating system ATutor is installed on - Microsoft Server Enterprise Edition 2003 with Service Pack 2
Achecker version - 1.0, latest stable release
Patch #s applied - none applied
Achecker theme name - use default
PHP version - 5.25
MySQL version - 5.0.51b Community Server Edition
Webserver & version - Apache 2.2.11
Copies of error messages - The following errors occurred:

Cannot connect to URL: intranet/

Changes to default settings - none

Cannot connect to URL: dev.icityville.com/>

Web browser being used - Internet Explorer 7.0.5730.13, 128 bit.
Posted: 2009-07-27 10:17:52
cindy

Avatar for cindy
Subject: Re:Quote this post in your reply
Because the URL entered in "Check Accessibility by URL" form field is invalid. For example, if you try to browser "dev.icityville.com/", will reach "Address Not Found" error.
Posted: 2009-07-27 10:39:50
andrewec
Subject: Re:Quote this post in your reply
Hi Cindy,

Thank you for your reply

But the http got converted into the hyperlinked url's above (plus I could have formatted the message a bit better).

I had included the http:// in my original check with achecker when I received the error messages.

Andrew.
Posted: 2009-07-27 14:32:54
greg

Avatar for greg
Subject: Re:Quote this post in your reply
What Cindy is saying is, the site you listed does not exist. So, naturally the not found error gets displayed.
Posted: 2009-07-27 14:52:17
andrewec
Subject: Re:Quote this post in your reply
Hi Greg,

Its behind our firewall and not exposed to the Internet, achecker installation is behind our firewall too, sry didn't mention earlier, other sites behind our firewall work fine with achecker.

Andrew.
Posted: 2009-07-27 14:57:45
greg

Avatar for greg
Subject: Re:Quote this post in your reply
There shouldn't be a problem testing an intranet site with a version of AChecker on that Intranet.

I don't have an answer for you. If you do eventually figure it out, let us know.

In the meantime, you can open the page at the site that doesn't check, save the HTML, and upload it into AChecker instead.
Posted: 2009-07-27 15:41:27
 Page: 1

You must be signed-in to post.