2
Single query approach
It seems there is no way to combine ListItem.GetWOPIFrameUrl method and ClientRuntimeContext.Load method.
I would propose the following solution.
Let's introduce the below method that returns the same result as as ListItem.GetWOPIFrameUrl method but does not require request to the server, instead it generates url based on List Item ...
2
You can run the below command to change the external url to the desired one.
Set-OfficeWebAppsFarm -ExternalURL "url"
Set-OfficeWebAppsFarm
1
Never, ever offload SSL. This creates an insecure environment passing tokens that are as good as a username and password between SharePoint and OOS. These can be intercepted and replayed.
But you have a mismatch between your WOPI zone on SharePoint and your ExternalUrl on OOS.
1
This feature is (now formerly) known as Office Web Apps for on premises installations. For SP Online, it’s known as Office Online (also see here) and acts as an integrated feature that is set to ‘on’ by default.
SharePoint on premise and SharePoint Online both have a server-side document processing system that will parse the contents of documents and ...
1
It turns out that the way to accomplish this is to set all the WOPI bindings except the "View" binding. If you have already been messing with the bindings, I would start by removing them all and adding them back:
Get-SPWOPIBinding –Application "WordPDF" | Remove-SPWOPIBinding -Confirm:$false
New-SPWOPIBinding -ServerName "your-server" -Application "WordPDF"...
1
The default OWA action is to open PDF files in WordPDF Application. To overcome this behavior, we can remove the WordPDF binding from OWA and let it open by Ifilter as default. Run the following command in SharePoint Application server where you configured OWA WOPI Binding. This command will remove the WordPDF Application Binding from your SharePoint farm. ...
Only top voted, non community-wiki answers of a minimum length are eligible