Forum Moderators: travelin cat

Message Too Old, No Replies

Need safari help

         

cfprogrammer

12:07 am on Jan 20, 2009 (gmt 0)

10+ Year Member



I am not sure if this is the best forum for this question but I am not sure where to turn. I think the answer is more in a server configuration than design as the design (the code) works fine on a staging server.

I have a page that uses mxData to load content into a div. The code all works fine on our staging server in IE, FireFox AND safari (windows and mac) but when I move the code to the production server the content doesn't load into the div and according to Service Capture the javascript isn't even try to fire in Safari. It works fine in IE and firefox just not safari.

The thing that doesn't make since is that safari does work on staging just not development. I have confirmed that all code on both boxes is identical. Both boxes are Window Server 2003, both running IIS6, both with CF8. I have look at the properties for the websites on both boxes and made sure their were also the same.

Any ideas at this point woul be very welcome.

Lance

travelin cat

12:34 am on Jan 20, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



cfprogrammer,

Welcome to webmasterworld.

Are you checking both servers with the same browser in the same session? Have you tried a different Mac to see if the problem was not just on the one Mac?

cfprogrammer

4:44 pm on Jan 20, 2009 (gmt 0)

10+ Year Member



Yes, I have tried several machines and the problem is not Mac (as Firefox on Mac is fine) it is safari. I loaded safari on a windows machine too to check that. The safari results are the same whether on a mac or windows.

I am sure it is a server setting somewhere but I can't find it. I just thought that maybe someone here had run into the same problem and knew how to fix it.

timster

5:51 pm on Jan 20, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Try to replicate this behavior in Opera (even if you aren't interested in testing for Opera). There are some ways in which Safari and Opera behave in common, and ruling that in or out may help narrow things down.

Another idea, have you checked your HTTP headers to ensure they are serving up identically across the staging and production environments?

Specifically, Safari is more strict about the way it handles malformed 302 (temporary redirection) headers.

cfprogrammer

6:43 pm on Jan 20, 2009 (gmt 0)

10+ Year Member



Opera now joins the list of browsers that behavior identically on staging and production and the site works correctly. So now for 8 possibilities (4 browsers on staging and production) only one fails, safari production.

The HTTP headers are also the same on both server. All the original IIS installation headers. There have been no redirects added.

I really apprieciate your help and suggestions of things to look at this has to be one of the most frustrating issues that I have ever encountered.