-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Return X-WOPI-Lock when a manual lock from outside exists #442
Conversation
Thanks a lot already. Just to double check does switching to the read only mode work for you for all file types (word/excel/PowerPoint)? |
Powerpoint: Locking works, but not read only Excel: More testing:
|
Also noted, the actual internal server error doesn't get logged anywhere afaik. |
The log messages indeed don't look related.
How do you trigger that and where you see it? Is there a request id mentioned in the output that could help find the log messages? |
Regarding the error that powerpoint shows, are you able to find something meaninful regaring the session id in the OOS server logs? I had a hard time checking those and also haven't noticed any message on mine that would indicate an error. |
Had one more confirmation that this fixes the issue as expected. |
I just try to open the document in the web as usual. Might have been something temporary.
Does OSS have seperate sevrer logs? 🤷♂️ |
Yes, see https://learn.microsoft.com/en-us/compliance/regulatory/gdpr-for-office-online-server and https://sharepoint.stackexchange.com/questions/286061/where-is-oos-loglocation-path-for-win2019 But I haven't found any useful message in there on my setup |
Signed-off-by: Julius Härtl <[email protected]>
Signed-off-by: Julius Härtl [email protected]
Summary
This change makes sure that we return a proper locked response in cases where an outside lock exists.
I've tested this change with word, excel, powerpoint, however on my OOS server switching to read only mode only work with excel. I couldn't figure out a reason for that yet, but as it seems to work fine with excel it would rather assume this is a bug or misconfiguration of my OOS server.
Checklist