Skip to content
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

OneNote 2016 needs a different user agent string #30962

Closed
mmattel opened this issue Mar 29, 2018 · 4 comments
Closed

OneNote 2016 needs a different user agent string #30962

mmattel opened this issue Mar 29, 2018 · 4 comments

Comments

@mmattel
Copy link
Contributor

mmattel commented Mar 29, 2018

Issue:
Webdav relevant. The user agent strings for Microsoft OneNote 2013 and 2016 are different.

For 2013 it is: (already implemented)
/Microsoft Office OneNote 2013/

For 2016 it is:
/OneNote/

Reference:
Please see:
https://www.webmasterworld.com/search_engine_spiders/4851195.htm
and
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_onenote-mso_win10/onenote-2016-authentication-issue-with-on-premises/1e136b4f-70b2-4f19-a636-4b14e5972bd8
Quote: "...OneNote 2016 user agent string starts with OneNote… "

Solution:
User agent string to be added at:

'/Microsoft Office OneNote 2013/',

and
'/Microsoft Office OneNote 2013/',

Note:
Looks like that Microsoft is removing any year or vendor info to be open for upcoming releases.

@ownclouders
Copy link
Contributor

GitMate.io thinks the contributor most likely able to help you is @PVince81.

Possibly related issues are #7370 (User Agent Strings), #27813 (Need the ability to list users), #563 (String Error?), #4055 (File Versioning needs User identifier), and #1333 (rename users).

@DeepDiver1975
Copy link
Member

@mmattel please submit a PR - we can easily merge and backport this. THX a lot!

@mmattel
Copy link
Contributor Author

mmattel commented Mar 29, 2018

closin, corresponding PRs are merged

@mmattel mmattel closed this as completed Mar 29, 2018
@lock
Copy link

lock bot commented Jul 30, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants