We are trying to integrate the developer version of onlyOffice and verify the functionality.
The document server of onlyOffice is deployed on the back end and is isolated. Front end pages cannot directly access it, and they need to be accessed through the nginx proxy.
We now find a problem:
The front-end opens the document editing page through the proxy address, but the document itself to be edited fails to load. Because we accessed the documentServer using a proxy address, the document address returned by the documentServer to the front-end page through the socket to load is the actual onlyOffice server address, rather than a URL starting with the proxy address. At the same time, socket communication seems to be an internal communication method between onlyOffice and the front-end page.
How to control the URL of the document for edit sent by webSocket to the front-end page to start with a proxy address?