Stop returning a self-signed certificate on first website load #13

Open
opened 2023-12-06 15:29:31 +00:00 by baptiste · 0 comments
Owner

Currently, when Tricot does not have a certificate for a website, it returns a self-signed certificate while it queries Let's Encrypt in the background.

This is a usability issue for people trying to host a website on the Deuxfleurs infrastructure: when trying the first time, the self-signed certificate makes it look like something is broken, and people do not think about refreshing 30s later (which is totally understandable).

Also, it's not a good feeling for people visiting the website just after Tricot has restarted or lost its certificates (although it should happen less often thanks to #9).

Currently, when Tricot does not have a certificate for a website, it returns a self-signed certificate while it queries Let's Encrypt in the background. This is a usability issue for people trying to host a website on the Deuxfleurs infrastructure: when trying the first time, the self-signed certificate makes it look like something is broken, and people do not think about refreshing 30s later (which is totally understandable). Also, it's not a good feeling for people visiting the website just after Tricot has restarted or lost its certificates (although it should happen less often thanks to #9).
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/tricot#13
No description provided.