Skip navigation
This discussion is archived

Page not viewable in Safari

25272 Views 304 Replies Latest reply: Dec 29, 2005 3:46 PM by Michael Kraskin RSS
  • Otto42 Level 6 Level 6 (9,070 points)
    Currently Being Moderated
    Dec 7, 2005 2:55 PM (in response to Tom Graves)
    You will also see that
    http://www.catalogueofships.com/ tries to call itself
    as well as the favicon.


    Probably irrelevant. favicon.ico is usually pulled up for any domain, by many different browsers. In GoDaddy's case, the forwarding there will attempt to forward that to the actual webpage as well (not to the favicon.ico on said webpage), which might cause a problem.
    AMD Athlon 64 X2 4200+ Dual Core, Windows XP Pro, Corsair 1GB Asus A8N SLI ThermalTake 680W XFX Geforce 7800 GTX
  • Jester Level 2 Level 2 (420 points)
    Currently Being Moderated
    Dec 7, 2005 3:05 PM (in response to Otto42)
    It sounds to me like Godaddy is trying to fix the problem of not being able to have a favicon show up in the address bar for forwarded and masked sites. This would be nice if they can get it to work, but for now it appears they have broken the forwarding trying to do this.

    If that is the case, I don't see why they can't revert back until they figure out a way to get it to work. I would like my favicon to come up on my forwarded address, but I would much rather have my website come up!
    PB G4 (1.67GHz 15"), PB G3, iMac SE, Mac II SE, Mac+, Mac OS X (10.4.3)
  • Eric Taylor Calculating status...
    Currently Being Moderated
    Dec 7, 2005 3:23 PM (in response to IanRagsdale)
    Yep, totally the case. OmniWeb has a way-cool feature called the Error Log (under the Window menu). Check the box in it for "Show HTTP Requests" and you will get a perfect log of the transactions between the web server and the web browser.

    Like so:

    Dec 07 16:19:30 http Rx: HTTP/1.1 302 Moved Temporarily
    Dec 07 16:19:30 Rx: http://www.ehsbands.org/
    Dec 07 16:19:30 Content-Length: 0
    Dec 07 16:19:30 Location: /?ABCDEFGH
    Dec 07 16:19:30 (null)

    Interestingly, OmniWeb seems to load the page with no problems, despite the fact it's using WebCore.
    Various... B&W G3 thru XServe G5
  • Matthew Wanderer Level 2 Level 2 (285 points)
    Currently Being Moderated
    Dec 7, 2005 3:32 PM (in response to Jory Raphael)
    I just wrote and received the following response from Godaddy:

    "Response from WILLIAM G
    12/07/2005 04:23 PM
    Dear Matthew Wanderer

    Thank you for contacting Customer Support.

    Apple recently released an update to Java, Version J2SE 5.0. There is a bug in this release that has caused forwarding to stop working properly for both the browsers Safari and Opera on Mac OS X. You will need to report this bug to Apple Computers using the Report Bugs feature from within the Safari menu. This situation was caused by changes in Java and not GoDaddy. Because of that a resolution is completely out of our hands. I apologize for any inconvenience that this may cause.

    Please let us know if we can help you in any other way."

    They claim it's the Java update, which is what I thought it might be in my initial post. Frustrating is just the beginning here because I quite sure Apple will pass the buck as well, and why wouldn't they.
    http://homepage.mac.com/cherrypop
  • Geoffrey Sperl Calculating status...
    Currently Being Moderated
    Dec 7, 2005 3:35 PM (in response to Michael Kraskin)
    After researching this myself (I have three domains with GoDaddy), it looks lke RegisterFly is the way to go.

    I'm not even going to bother asking GoDaddy to help - I've read the notices here. I'm just going to leave them.

    Is there anyone here who suggests not using RegisterFly?
    PowerBook G4, Mac OS X (10.4.3)
  • ZackMac Level 1 Level 1 (15 points)
    Currently Being Moderated
    Dec 7, 2005 4:00 PM (in response to Michael Kraskin)
    Amen Michael!

    And I'm not passing blame when I say it is GoDaddy's fault.

    I'm saying who's responsibility it is to fix it.

    For example, if I rolled out an update on my own personal website that locked out Firefox users and I was informed about it, I wouldn't ask the Firefox developers to fix Firefox because my website doesn't work with their browser.

    I'd find a workaround on my end - at the web page end - that would resolve the problem. In fact, I'd probably revert to a previously known working version of the page until I could properly test and resolve the issue. If I found the issue was nothing on my part then I would certainly then check Bugzilla and so forth and go at it from that angle, but I would probably withhold my change until I was certain the major three web browsers (IE, Firefox & Safari) worked well with my site. This is called testing. You don't move something into production that doesn't work as intended.

    GoDaddy is first a domain registrar. Domains are platform independent. Simple stuff like website forwarding and masking should be platform independent and not be reliant on a certain feature sets of available in only some browsers. I mean, c'mon, it can't be that hard to make something work with at least the big four - IE, Firefox, Safari & Opera.

    Here are the facts
    1. This blank page issue did not occur because of any release in Java (I didn't update)
    2. This blank page issue did not occur with the release of Safari 2.0.2 (I using 2.0.1) or the release of Mac OS X 10.4.3 (I'm at 10.4.2).
    3. My domain forwarding has worked for years (literaly, almost three years if not more) without a hitch and stopped without any updates from Apple.

    This leaves me to conclude that GoDaddy made a change on their end to how their domain forwarding works. My push is on them to fix the problem or revert back to the old way of doing it. See my example above about my personal website - if my code broke a browser, I'd find a way to fix it or withhold the release. (ie. testing!).

    Further research does seem to show that GoDaddy is indeed trying to do two new things - 1. Load a favicon of a masked website and 2. stop potential phishing websites from using their forwarding services to mask themselves as Paypal or your bank, etc. They could also be attemping several other types of antiscam or general features in this recent domain forwarding release.

    I'll say it again - While Safari and Opera are the ones showing the blank page, it isn't exactly a bug in Safari or Opera causing this problem, it is a change that GoDaddy could simply revert until a mutual resolution could be found. Again, see my personal website example above.

    I don't understand GoDaddy's logic - how can they expect Apple to fix a website glitch that is due to their malformed headers? The nerve!
    Power Mac G5 Dual 2.5Ghz | Powerbook G4 867 | Power Mac 'Quicksilver' G4 733, Mac OS X (10.4.2), Safari 2.0.1
  • Jeff Holdaway Level 1 Level 1 (40 points)
    Currently Being Moderated
    Dec 7, 2005 4:08 PM (in response to Tom Graves)
    Ok. well In case this wasn't answered yet and you get to my response I will let you know exactly what is going on.

    The domain MASKING used by godaddy is not incompatible with Safari but has been disabled. So turn off your Domain Masking if you want your site to work on Safari.

    WHY? You ask. Well the short answer is security. Phishing is a real problem and Domain Masking is a big part of phishing. GoDaddy masking wont put wellsfargo.com as a mask on your web forward. However phishers and spammers don't have a problem with it.

    Masking is bad form anyway. If you cannot afford a web server like me, try a shared server like bluehost.com (it cost less then 200 bucks for two years [$7 a month] and i can host 6 websites so you can make your money back easy.

    And even if you don't want to pay a dime above the 9 bucks a year, as long as you can find a webspace without popups then people will not mind the forward taking you from mydomainwhateveritis.com to myipwhateveritis.com/~me You will thank yourself even more when IE7 comes out next year with its super secure phishing features.
    powerbook, Mac OS X (10.4.3)
  • Jeff Holdaway Level 1 Level 1 (40 points)
    Currently Being Moderated
    Dec 7, 2005 4:37 PM (in response to Michael Kraskin)
    Just be warned.. Godaddy will work if you take off the masking. And if you go elsewhere and get masking it will also not work (most places don't offer it). You don't want it anyway.. you want to have a nameserver to put the domain address into your address
    powerbook, Mac OS X (10.4.3)
  • ashiver Calculating status...
    Currently Being Moderated
    Dec 7, 2005 4:50 PM (in response to Jeff Holdaway)
    no. removing masking does not work. I have done it before and have now done it again. same results. blank page.

    this is beginning to become ridiculous.

    I don't have extra cash just lying around to throw at transfering my domains right now. it is after all the holidays. so I am stuck with this poor service. which is surprising considering before this I'd had absolutely no issues with GoDaddy's forwarding, masking or hosting.
    12" Powerbook G4, Mac OS X (10.4.3)
  • J Deschamps Level 2 Level 2 (215 points)
    Currently Being Moderated
    Dec 7, 2005 4:54 PM (in response to Michael Kraskin)
    GoDaddy.com Hates Mac Users

    wow we're currently number 1 on digg!!! 1870 diggs and counting!!!
    http://digg.com/topstories
    17 powerbook g4, Mac OS X (10.4.3)
  • ashiver Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 7, 2005 4:58 PM (in response to J Deschamps)
    wow. maybe we'll make it onto this week's diggnation pod/video-cast. I doubt it though considering their sponsorship of their show.

    keep digging everyone!
    12" Powerbook G4, Mac OS X (10.4.3)
1 ... 14 15 16 17 18 ... 21 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.