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.

Sign up for GitHub

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

Jump to bottom

Request wildcard certificates #406

Open
Riscky opened this issue Jun 8, 2022 · 1 comment · May be fixed by #387
Open

Request wildcard certificates #406

Riscky opened this issue Jun 8, 2022 · 1 comment · May be fixed by #387
Assignees
@Mstiekema
Labels
enhancement Proposes (changes to) a feature maintainability

Comments

@Riscky
Copy link
Member

Riscky commented Jun 8, 2022

Currently, we have separate certificates for most of our subdomains.
For example, koala.svsticky.nl has a separate domain from photos.svsticky.nl
It would be faster, and more convenient, to use a wildcard certificate instead.
This is WIP, see #387
@Riscky Riscky linked a pull request Jun 8, 2022 that will close this issue
Wildcard certs #387
Open
@Riscky
Copy link
Member Author

Riscky commented Jun 8, 2022

This would also make sure that non-existing subdomains don't give a 'no ssl' message, but instead redirect to the main website.
We might also want to give a 404 here instead of redirecting.

@SilasPeters SilasPeters added enhancement Proposes (changes to) a feature maintainability labels Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Mstiekema Mstiekema

Labels
enhancement Proposes (changes to) a feature maintainability
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Wildcard certs svsticky/sadserver
3 participants
@Riscky @Mstiekema @SilasPeters