Safari [Archive] - Wildcat Nation Forums - Kentucky Wildcat Discussion and News

PDA

View Full Version : Safari


ryanebelhar
01-15-2007, 05:54 PM
I'm on a mac, and I can view this site in Firefox, which is what I'm doing now. But my browser of choice is Safari. Everytime I try to look at the forums with Safari I get an error message. Is there are a reason that you know of? I hate having to use two browsers just to look at one site.

Thanks

Ryan

WildcatDan
01-16-2007, 08:30 AM
If you let me know what the error message is I will research it and get back to you... Since I have such a small knowledge of Macs I just have no idea off the top of my head!

Jeff Craddock
01-19-2007, 08:57 PM
I generally post using Camino or Firefox, but this is being posted from Safari 2.0.4. No problem doing this on my PowerBook. Maybe you should report this to Apple as a bug, in the Safari dropdown box, just below "about Safari".

I generally find Safari to be a shade slower than my other two browsers, so I don't use it much.

ryanebelhar
01-22-2007, 09:35 AM
Safari can’t open the page.
Safari can’t open the page “http://www.wildcatnation.net/forum/view_topic.php?id=30776&forum_id=2”. The error was: “bad server response” (NSURLErrorDomain:-1011) Please choose Report Bug to Apple from the Safari menu, note the error number, and describe what you did before you saw this message.

Coldstream
01-22-2007, 03:06 PM
ryanebelhar wrote:
Safari can’t open the page.
Safari can’t open the page “http://www.wildcatnation.net/forum/view_topic.php?id=30776&forum_id=2”. The error was: “bad server response” (NSURLErrorDomain:-1011) Please choose Report Bug to Apple from the Safari menu, note the error number, and describe what you did before you saw this message.

I'm using our Mac test box we used for testing our company's website here. I am not able to reproduce the issue you are reporting. :shrug:

However, I googled the error code above and found some advice:
NSURLErrorDomain:-1011

I also use direcway and get the bad server response, seemingly at random. I found that emptying the cache (from the Safari menu) and clearing the history (from the History menu) works.

It doesn't appear to be a problem with the website itself but the way Safari behaves???