The hash value sent by the backend is based on the original path which gets validated against the local path used to open excel on the user machine. In the direct scenario, the path matches and we don't see an issue. In rewritten case, both hash values will not match as due to rewriting the hash will be different on the endpoint side & hence there is no way for us to make them match as it breaks rewriter functionality altogether and the request goes direct making the file open fail.
We are good to conclude this as a Pulse limitation due to changes made by Microsoft and there is no way that we can handle/fix this limitation. |