-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
feat(ILOC): allow custom URL schemas #101197
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
base: master
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #101197 +/- ##
===========================================
+ Coverage 81.11% 81.17% +0.06%
===========================================
Files 8595 8624 +29
Lines 380872 382792 +1920
Branches 23899 23899
===========================================
+ Hits 308954 310746 +1792
- Misses 71556 71684 +128
Partials 362 362 |
return data | ||
|
||
if data == "": | ||
self.fail("invalid") |
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.
parsed = urlparse(data) | ||
if not parsed.scheme or not parsed.netloc: | ||
self.fail("invalid") |
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.
Should we disallow custom schemes that overlap with known protocols? I'm thinking of things like file://
, ftp://
, irc://
, mailto://
, javascript://
, odbc://
and s3://
?
Allow for custom redirect URI schemas to allow the mobile app to respond to a non-HTTP redirect for its auth. See https://www.notion.so/sentry/Seer-Mobile-Auth-2628b10e4b5d80e589dcdbb2e03782d5.