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

Deep Link Action Handler #1421

Closed
enijar opened this issue Apr 1, 2021 · 4 comments
Closed

Deep Link Action Handler #1421

enijar opened this issue Apr 1, 2021 · 4 comments

Comments

@enijar
Copy link

enijar commented Apr 1, 2021

Feature Description
I'm unsure if the correct term is "deep link", but I've seen this on several website to desktop app links, where (for example) you click on a website link and that link opens the corresponding desktop app (if installed) and performs an action. An example of this is Discord invite links.

Here is a contrived example of a "deep link":

appname://action/path?arg1=val1&arg2=val2

This would be linked to from a website, with a normal anchor tag:

<a href="appname://action/path?arg1=val1&arg2=val2">Open appname</a>

I think this would be a nice featuer for Tauri to support, allowing developers to link to their desktop app and handle incomming actions.

@nothingismagick
Copy link
Member

There is a VERY old issue about this, that we definitely want to resolve as soon as the beta-rc lands.
#323

That said, there are very serious concerns about security of deeplinks, so I think that this should probably be a tauri plugin.

@enijar
Copy link
Author

enijar commented Apr 1, 2021

Thanks for linking for the issue. I did a search for issues with "deep link", didn't know it was called "URI scheme" 👍

@enijar
Copy link
Author

enijar commented Apr 1, 2021

Appologies for the ignorant question, but what exactly are the security concerns with URI schemes?

@nothingismagick
Copy link
Member

Technically any application can register such an URI scheme with your host operating system. Furthermore, I consider this to be a type of "push message" that your application MUST parse even thought it has no way of authenticating the sender, since these deeplinks are generally (always?) intercepted by the browser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants