OK, I give up on trying to figure out what to search for in Bing!
I have a SharePoint 2013 farm that has been connected to an Office Web Apps server and working just fine. We are going to be changing the hostname for the primary web application, so I extended the web application to the Intranet zone with the new host name. Both are HTTPS only. After set up was completed and the F5 load balancer correctly configured, you could go to webapp1.foo.com or webapp2 (using the short name on the Intranet zone) and everything worked fine. The preview pane loads Office documents and you can open office documents in the approprate Office Web App.
In our qual environment, I then implemented a redirect from webapp1.foo.com to webapp2 using URL Rewrite. This places a redirect rule in the applicationHost.config file, which you have then manually add a couple of things to, but after that the redirect was working fine; except that Office Web Apps no longer works. There are a variety of error messages, depending on the type of document you are trying to preview/load:
- Unable to Open the File. We couldn't find the file you wanted. It's possible the file was renamed, moved or deleted;
- Sorry, we are having a problem showing this workbook. Something is preventing us from opening the workbook. It might be blocked for security reasons;
- Microsoft Word Web App. Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word;
ULS logs on both SharePoint and OWA aren't showing anything particularly useful, nor is the Event Viewer. The issues I'm seeing are similar to ones others have reported, but I've gone through the potential fixes and nothing works. Again, it works fine so long as the redirect isn't there, but if the redirect is active, I have issues whether or not I start with the webapp1.foo.com and get redirected or start with webapp2, which theoretically shouldn't trigger the redirect at all. BTW, I also tried using just the HTTP Redirect.
Server OS is Windows Server 2008 R2 for all servers. I'm just at a loss on what to try next. Has anyone else experienced this issue?