sdk do NOT support dsn with subpath

[lumincui]

By some reason, we can't use a absolute domain for sentry, so we use subpath instead like company.io/sentry/project_id. But sentry-python think project_id as int, and think the dsn above is invalid.

Exception:

sentry_sdk.utils.BadDsn: Invalid project in DSN (u'sentry/848')

[untitaker]

Which version of sentry (server) are you using? I am told that we just don't support subpath installations anymore since at least 2017: getsentry/sentry#5174

[untitaker]

We're going to backport this anyway due to proxies running in front of sentry.

[lumincui]

@untitaker Version 9.0.0

[untitaker]

Will be fixed in the next release. Thanks for your patience!

[mitsuhiko]

Reopening because we need to revisit this. Not supporting subpaths was an intentional change and is already not supported in a lot of environments.

[mitsuhiko]

@vincenthcui how do you have sentry deployed that sentry is at a non root path? That should not work.

[untitaker]

As discussed this is at least useful when you have a reverse proxy specifically for store. I don't see the harm in having it

…

On Thu, Jan 3, 2019, 00:22 Armin Ronacher ***@***.*** wrote: @vincenthcui <https://github.com/vincenthcui> how do you have sentry deployed that sentry is at a non root path? That should not work. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#212 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAzHxa0ybYd60DI7Ws-uAfl80bHYegEUks5u_T9JgaJpZM4ZV7oq> .