[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

WEBrick Issue with IE: Page Not Found, Cannot Connect to Server

franksjonathan

1/12/2006 3:09:00 AM

I'm working on a Ruby on Rails project. I had a catastrophic notebook
failure earlier this week so I moved everything over to a new machine.
I installed a new version of Ruby, Rails, WATIR, Eclipse, and
everything else I need and I am experiencing a problem that none of our
other 3 development machines had.
When I fire up WEBrick from either a command prompt or my external tool
menu in Eclipse, it seems to load up fine and I can hit my Rails app in
Firefox from my machine and from other computers.
I can't use Internet Explorer to connect to WEBrick! localhost:3000,
127.0.0.1:3000, nothing works. Firefox responds beautifully to both
addresses on port 3000.
Now I did notice a behavior I don't fully understand: When I navigate
to localhost:3000 it replaces the value in the address bar with
local:3000.
I'm all kinds of confused about this problem. It manifests in a number
of ways, and I am open to the possibility that this may be several
problems coming up all together.
If I use Firefox I can browse to WEBrick running on other computers in
addition to my local instance. If I use IE on this machine, I can't hit
my own WEBrick, and I can't hit the WEBrick of the other developer's
machine. I can't use IE on another machine and hit my local instance of
WEBrick here, but I can use Firefox on another machine and connect to
it.
What can I do to make IE play nicely with WEBrick?
Thanks!
Jonathan

3 Answers

Vivek

1/12/2006 3:46:00 AM

0

you will get a better answer at the rails list.
but the behaviour you observe is strange..IE replaces localhost to
local? never heard of this!

james_b

1/12/2006 3:47:00 AM

0

franksjonathan@gmail.com wrote:

> Now I did notice a behavior I don't fully understand: When I navigate
> to localhost:3000 it replaces the value in the address bar with
> local:3000.


Try clearing the IE cache. See about turning off auto-completion of
URLs, too.

Also try an explicit protocol prefix:

http://127....

And consider adding an entry to your hosts file

127.0.0.1 www.example.com

and trying it with that bogus domain:

http://www.exampl...

If you have something like wget, fetch the page and inspect the headers
to see if anything looks odd.


James

--

http://www.ru... - Ruby Help & Documentation
http://www.artima.c... - The Journal By & For Rubyists
http://www.rub... - The Ruby Store for Ruby Stuff
http://www.jame... - Playing with Better Toys
http://www.30seco... - Building Better Tools


franksjonathan

1/12/2006 6:23:00 AM

0

The explicit protocol seems to have done it! I can connect with
http://127.....
Thanks a lot, James. Work may resume as normal.