Hi: Web browsers in general assume that the user means www in front of a URL. While this has been true in the past, there is no reason why a web sever has to be configured to respond to www.domain.xxx. Camino does the same standard thing but it often gets in the way of accessing some servers that do not respond to www.
This morning I attempted to get to http://vsbeducation.ca . Camino promptly tried to reach www.vsbeducation.ca. I got to the address by using a back door method I know about. That redirected me to vsbeducation.ca. To compare behaviour, I ssh'd to another machine with a different outside ip address and used lynx to the same site and got there immediately. By design, www.vsbeducation.ca does not exist. Is the default to www a part of any web standard? (I thought that it was only http:// which determined the protocol) Is there a way to turn off this default behaviour and make Camino be little more literal in the way it responds to user requests? Is this behaviour in anyway affected by URL completion preference? Another one which happens with regularity is getting www.htttp when I've typed an address using the full URL. It is possible that this is a combination of my typing error and Camino's default behaviour. (I've been trying to trace back exactly what I did when this happens) Someone has registered www.http.com and many others users get to with a little assistance from a helpful browser. Software can be to helpful sometimes. As annoying as they may seem, a real error message is frequently more helpful than leaping to a conclusion that you really wanted this instead of that. Google gets it right when it asks "Did you mean XXX?". I can choose to ignore Google's helpful hint or say yes. Google is only right about 50% of the time if that. David -- "Music is enough for one's life time, but one life time is not enough for music" Sergei Rachmaninov _______________________________________________ Camino mailing list [email protected] http://mozdev.org/mailman/listinfo/camino
