REBOL/Core 2.5.6.3.1 error.

[leke]

I tried to run REBOL/Core 2.5.6.3.1. from a floppy on the internet at my library. I got this error though when I tried something simple like opening a web page.

REBOL/Core 2.5.6.3.1
Copyright 1997-2003 REBOL Technologies
REBOL is a Trademark of REBOL Technologies
All rights reserved.

Component: "REBOL Mezzanine Extensions" 1.1.2.1 (29-Nov-2002/19:29:09)
Component: "REBOL Internet Protocols" 1.59.2.15 (14-Feb-2003/1:45:14)
Finger protocol loaded
Whois protocol loaded
Daytime protocol loaded
SMTP protocol loaded
POP protocol loaded
IMAP protocol loaded
HTTP protocol loaded
FTP protocol loaded
NNTP protocol loaded
Component: "System Port" 1.1.2.5 (30-Nov-2002/17:24:03)
>> read http://www.reboltalk.com/
connecting to: www.reboltalk.com
** Access Error: Cannot connect to www.reboltalk.com
** Where: open-proto
** Near: read http://www.reboltalk.com/

I know  the libraries computers have some security features that stop you from doing certain things but is there anything I can do to use core regardless?
Thanks,
L.
 

[Sunanda]

Can you get a result with othe sites, eg

read http://www.rebol.com

---

My first answer would have been that the correct url for reboltalk should be:

read http://reboltalk.com

because it never used to respond if you added www.

But I notice it does today -- so do you still get the same failure as you reported yesterday?
 

[Guest_leke]

Yes, I get the same error for sites I even type correctly.  

[Sunanda]

Okay, so maybe your local library has its Internet access locked down pretty tight. In some ways you'd want them to do that. So you may be failing to reach across a firewall.

(In my Library the floppy and CD/DVD slots are blocked off, so I couldn't even get as far as you have).

Can you get local access:

 read http://localhost/

or

 read http://127.0.0.1/

After your read fails, there should be a global (yes, global!) variable, response-code

It'll contain the HTTP server status code. Might help.

[leke]

Ok, will give it a try next time I'm there. Thanks.

[leke]

This was displayed after the READ fail...

>> read http://localhost/
connecting to: localhost
** Access Error: Cannot connect to localhost
** Where: open-proto
** Near: read http://localhost/

Then I tried...
>> read http://127.0.0.1/
connecting to: 127.0.0.1
** Access Error: Cannot connect to 127.0.0.1
** Where: open-proto
** Near: read http://127.0.0.1/
>>

Seems like the security is doing its job (nice to know).
Thanks anyway.
L.