8 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I am having the same problem and noted the same thing with Firefox working and Safari not.

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Go up to Safari (upper left corner next to Apple logo)
    Then to Preferences > Security > Show Cookies> type in Drudgereport.

    Delete all DR cookies that show up.
    Restart Safari.

    Any Better?

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    That did the trick. Thank you!

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    EXCellent!
    Glad you're all sorted now!

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thank you too--that worked for me too. (Not sure why but that's not important!)

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Very good, James.
    That's what's great about these forums . . .
    Solutions just keep on going, and going, and going . . .
    Thanks for letting us know.

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ditto
    Drudge report must be somehow hacked or disabled. I get the 414 message about 99% of the time.

  8. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks! This tip also worked for a "413 request entity too large" error I was getting after installing Safari 4.0.5. Glad I found your solution, I was baffled Firefox would load the page but Safari wouldn't.

    Bad cookies!
    413 request entity too large