能否重定向WOPI REST调用获取SharePoint文件？求流程优化方案

Great question—integrating Office Online via WOPI with SharePoint files can definitely be optimized beyond the current download-and-forward approach. Let’s break down your options:

Option 1: Redirect WOPI Requests Directly to SharePoint's Native WOPI Endpoint #

This is the most impactful fix for both speed and stability, since it eliminates your app as a middleman entirely. SharePoint includes a built-in WOPI endpoint (/_vti_bin/wopi.ashx) that Office Online understands natively. Here’s how to implement it:

• When your WOPI service receives a getFileInformation or getFile request, instead of fetching the file via Graph API, generate the SharePoint WOPI URL for the target file. It will look something like:

  https://your-sharepoint-site.sharepoint.com/_vti_bin/wopi.ashx/files/<unique-file-id>
  

• Return a 302 Redirect response to this URL, and include the valid access token (obtained via Microsoft Graph API) in the Authorization header of the redirect.
• Office Online will follow the redirect and communicate directly with SharePoint’s WOPI endpoint, skipping your app’s download/forward step entirely.

Key Notes: #

• Ensure your app has the necessary permissions (e.g., Files.ReadWrite.All or site-specific Files.ReadWrite permission) to generate a token that SharePoint’s WOPI endpoint accepts.
• You don’t need to handle CORS here—Microsoft’s services are already configured to work together seamlessly.

Option 2: Optimize the Existing Graph API Download Flow #

If redirecting isn’t feasible right now, you can tweak your current workflow to reduce latency and improve reliability:

• Use partial requests for large files: Instead of downloading the entire file at once, use Graph API’s range requests to fetch chunks of the file. This avoids timeouts for large .pptx or .docx files.
• Cache file metadata: Store the getFileInformation data (like file size, last modified time) in a short-term cache (e.g., Redis) so repeated requests don’t require a fresh Graph API call.
• Batch Graph API requests: Combine multiple related Graph calls (e.g., fetching file metadata + permissions) into a single batch request to reduce round-trip latency.
• Use region-specific Graph endpoints: Call the Graph API endpoint closest to your app’s hosting location to minimize network delay.
• Avoid unnecessary data fetching: Use $select in your Graph API calls to only retrieve the fields you need for getFileInformation (e.g., id, name, size, lastModifiedDateTime) instead of the full file object.

Option 3: Use Direct Office Online Embeds (For View-Only or Simple Scenarios) #

If your use case is primarily viewing files (not full editing), you can skip WOPI entirely and embed Office Online directly using the file’s SharePoint URL. Construct a URL like:

https://view.officeapps.live.com/op/embed.aspx?src=<encoded-sharepoint-file-url>

You’ll need to ensure the user has valid access to the SharePoint file (either via their own credentials or a shared access token), but this avoids the WOPI middleware layer altogether.

内容的提问来源于stack exchange，提问作者Gandhali Ambike