Hello, One way might be to access SAS Content Server as regular WebDAV server. And copy xml files with report definitions from there to repository location. And then run git to keep record changes. It will not track changes in report metadata, just in report content. Also understanding changes might be a bit tricky - requiring knowledge of SAS Visual Analytics report xml format. Thus going from xml change to action in web interface - what was clicked - might not be obvious. On other hand, plain revert to some yesterday version should be simple. With just substitution of xml file.   Now, as always in git, for version control to be really useful, it would be nice if commit action would contain author's comment about changes. Here it is rather a process in the background that periodically(daily?) commits changes without understanding them.   Regards   Jan Alboszta     ... View more

Hello, To diagnose it I think you should use browser web developer tools. That way you could see all requests send and received.   I think the cause of observed behaviour is that your first request is indeed "/" and it gets proxied to /SASVisualAnalytics. However next redirect is to /SASLogon and then after confirming guest access I expect /SASVisualAnalytics/guest.jsp  request will be send, and that does not fall into your rule anymore. Maybe creating custom index page on SAS Web Server with iframe would work for you?   Regards   Jan Alboszta ... View more