Safari can’t open the page.
every time i type http://delicious.com/ on safari i get Safari can’t open the page “http://delicious.com/”. The error was: “bad server response” (NSURLErrorDomain:-1011) Please choose Report Bugs to Apple from the Safari menu, note the error number, and describe what you did before you saw this message.
and of couse i cant access my user
and of couse i cant access my user
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?We've heard several other reports of this in a forum thread. Here's our response: "This actually appears to be a bug in Safari/OS X 10.4.x, but we are looking for a work-around to get the site back to being accessible for these browsers. In the mean-time you should have no problems accessing the site in Firefox."
-
Safari 3.1.2 on OSX 10.4 - can't open delicious at all - can only post and view delicious items on Firefox. This has only gone on for a week, and I can access every other site on Safari without problems. That suggests the fault is at delicious!
Safari has upgraded their site programming and now requires programming with a direct reference to Safari capabilities, rather than "do it like Firefox" or "do it like Explorer"; I had to reprogram my own site to make it work on the newest version of Safari and expect that delicious programmers need to do that also. -
See below — I believe that the problem is related to Safari's handling of compressed pages. -
Inappropriate?i very much doubt that. you mean to tell us when i type www.delicious.com is a Safari/OS X 10.4.x bug.
what a coincidence then since i just browse over 200 websites a day & yours is the only one.
let me make it easy for all of us. IN THE MEAN TIME
http://ma.gnolia.com/
http://www.toprankblog.com/tools/soci...
http://www.diigo.com
I’m indifferent
-
Inappropriate?Yes, it seems that something about how we compress pages (to make them load more quickly) triggers a bug in certain versions of Safari — see this bug report for example. That's why the error page looks like a Safari error instead of a Delicious error. It also happens in Mac OS 10.5.4 but not in 10.5.5, so I believe that Apple was aware of it and fixed it in that recent upgrade.
We're investigating a way to avoid triggering that bug so that people don't have to upgrade their systems in order to use Delicious in Safari. -
& this leaves the conversation where... i mean do i need to buy a new operating system or a new computer to use delicious. ok firefox is an alternative however but not good enough -
I recommend using Firefox for now. I'm hoping that we'll be able to find a good workaround for Safari soon. If you'd like to buy Mac OS 10.5 — for example, if you were planning to upgrade soon anyway — that would also be a way to avoid this error (although a somewhat expensive way). -
Inappropriate?I hope you find a workaround. My message from delicious tech support said that it was Apple's problem, which led me to worry that delicious didn't care if all pre-OSX 10.5 Safari users were bumped off the system.
now that I've come to depend on delicious, I'd prefer to continue to be able to use it without changing my browser or my computer!
I’m concerned
-
Inappropriate?A few days ago we released an update that should have fixed this. Please let us know if you continue to get weird Safari errors.
-
I upgraded to Leopard last week and I dont have the problem. But now I cannot give you feedback about Tiger. -
Inappropriate?Britta, I'm a web developer working on a site with the same issue. What did you guys do to fix this?
-
Inappropriate?This problem went away for me when I upgraded to Mac OS X 10.5.8.
-
Inappropriate?Avi, that won't fix the problem for thousands of end users who run G3 or G4 Macs whose max operating system is OS X 10.4.11 and Safari 3.2.1, where the problem is particularly nasty. I can't just tell people to upgrade, because that would be lazy of me. But thanks for your input - it's good to know that...
-
Sorry for my late response — did you ever figure this out? The problem happened a year ago for us, so I don't remember the details, but I believe people started seeing the error when we implemented a certain kind of gzip compression on our pages.
Loading Profile...



EMPLOYEE
