none
SharePoint 2013 SSRS SQL 2012 SP1 and Mac Safari 5.1 or 6.0 report issues

    Question

  • I have been try to figure out an issue that only seems to be affecting Safari 5.1 or 6.0 on OSX 10.6.8 or 10.7. I can view the same reports as the same user on the same Mac as the same user in Chrome 27.0.1453.116 or Firefox 22.  I have also tested iPads (iPad2 iOS 6.1), Android tablets and phones (ICS 4.0.4 and JB 4.2.2), and even an Microsoft Surface and they all work fine.

    The issue is when viewing a report through SharePoint 2013 in Safari regardless of if the report has parameters or not is it looks like the page just keeps reloading. The problem is not that I can't see the report viewer which is most of the issues related to SSRS 2008R2 and 2012. I can see the report view and I can even put in parameters. However when I click Apply the follow activity occurs.

    On Safari the following occurs

    POST: RSViewerPage.aspx

    GET: 302 Found default.aspx /_login: Size 0B, Transfer 1.67KB

    GET: 302 Found default.aspx /_windows Size 0B, Transfer 1.15KB

    It seems like the browser is redirected to login again. If I do this with a report that does not have parameters the "Loading" gif will appear forever with the same cycle going on with the page loading over and over. I did read something about Safari not supporting pass through authentication in 5.1. However if that is the problem then why is Safari listed as a supported browser, or not listed with that caveat on the browser support page?

    In Chrome this same set of step 302 to occur if I do not use the report for a while. After hitting apply the report appears to refresh to a blank report without any parameter values selected. The POST/GET activity mimics what I am seeing for Safari.  However unlike Safari, if I immediately put the parameters in again and click apply the report works as expected. Also when the report loads as expected I do not see the 302 to default.aspx /_login and /_windows.

    So what is different about Safari on OSX that is preventing it from displaying reports correctly when just about every other supported OS/Browser combination including some that aren't officially supported work perfectly fine with the same report?


    • Edited by K_Laubscher Monday, July 08, 2013 8:29 PM Added SharePoint 2013 information
    Monday, July 08, 2013 5:18 PM

All replies