IE bug help

Off-topic
1

My laptop crashed and I had to reload a bunch of programs.

IE 6.0 is now automatically trying to append “www” and “com” to URLs that don’t need it. For example, I try to go to http://news.google.com and it insists on trying to access http://www.news.google.com.com .

And just for the record, if it matters to anyone, there is one particular website I use that is optimized for IE and I need to use it for this. I use it to find articles for the "Unicycling articles (but wait there’s more…) thread.

Anyone encounter this and know what settings I need to change?

Thanks!

2

I’m pretty sure it’s something under ADVANCED in the INTERNET OPTIONS available from the TOOLS drop down menu, but I assume you’ve had a look in there and without knowing exactly what to do, this isn’t really helping.
And since this thread is still at the top, it doesn’t even count as a ‘till-john-childs-gets-here-bump’.
Oh well, just imagine I just popped in to say hi.

3

That’s where just about everything useful is.

I don’t have a Windows machine handy, but this sounds like either default behavior, or possibly a function of one of Microsoft’s auto-correct features. In other words, if you can’t find it in IE, have a look at your auto-correct settings in Office (Word). But it may just be a preference setting somewhere in IE.

Then of course there’s Firefox…

4

Indeed there is. Ignore John Childs, he’s wrong… :slight_smile:

Phil

5

Did you ever get this sorted out Raphael?

6

mmmm firefox

7

As a matter of fact I did. But truthfully, I think it just went away on it’s own.

8

I think it was a problem at your ISP’s or corporate-network resolver.
The www. and .com only will be appened

  • if it can’t find a IP for dns name,
  • if at the found IP of a hostname there is no :80 open
    So; if news.google.com got www. .com appended you must have had a problem in your (home?) network (which is more likely as a DNS problem at Google -which of course is possible as well-).
    The problem got solved once the resolving namer nameserver(s) started to function normally again -or were being reached again- (and leaded your webbrowser to the right location).