FQDN trailing dot doesn't work in DSN

[torgeirl]

How do you use Sentry?

Self-hosted/on-premise

Version

2.59.0

Steps to Reproduce

To limit DNS lookups, reduce latency and avoid unnecessary logging within a container environment it is good practice to provide absolute FQDN including the trailing dot for your services, ie.

• PSQL server: psql-host.company.com. <- notice the dot!
• Sentry DSN: https://project-hash@sentry.company.com./N

For a Django 5.2 application the PSQL host name works fine with the trailing dot and other on-premises services (but not all) will also accept addresses that include trailing dots, but when the trailing dot is included in the Sentry DSN it doesn't show up as an issue on the on-premise server.

Steps to reproduce

1. Test that it works without trailing dot, in Django project's container:

$ python manage.py shell
>>> import sentry_sdk
>>> print(sentry_sdk.Hub.current.client.options.get('dsn')) # <- verify DSN
https://project-hash@sentry.company.com/N
>>> sentry_sdk.capture_message("Hello world", level="error")
'event-id' # <- this will be the event ID for the issue in Sentry

... and if you see in Sentry you will have a new «Hello world» issue that has that event ID.

2. Change the DSN in your enviroment, repeat the steps above and see that it looks the same apart from the issue never reaching your Sentry server.

Expected Result

When the trailing dot is included in the DSN an issue would still reach our Sentry server.

Actual Result

The issue/event seems to be discarded, probably due to SSL issues caused by Sentry/Sentry's dependencies not handling FQDN correctly.

[linear-code]

PY-2405