-
Notifications
You must be signed in to change notification settings - Fork 113
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
Resolve a WOPI bridge appProviderURL #1234
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
7eb0fad
to
af822c8
Compare
|
||
// In case of applications served by the WOPI bridge, resolve the URL and go to the app | ||
// Note that URL matching is performed via string matching, not via IP resolution: may need to fix this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is ready for review, and I explicitly bring the attention to this note ;-) Feedback welcome.
af822c8
to
4fcbfbd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @glpatcern, apologies for the delay in the review. Just a minor nit, rest looks good.
531c835
to
a6d426e
Compare
a6d426e
to
1b9847d
Compare
A minor addition to simplify user interaction: if the
AppProviderUrl
is to be served by the WOPI bridge, resolve it byGET
ting it and returning the redirected URL as the realAppProviderUrl
value.