caddyserver / caddyserver/website
Update wildcard pattern example in line with 2.10.0 changes to default handling of wildcard certs
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 227
- Forks
- 213
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 1
Description
I started using caddy a few days ago, and per the relevant documentation, I set up my Caddyfile as suggested in the wildcard pattern.
It worked with my first reverse proxy subdomain, but when I added the second one, I could not get it to work.
After much searching and experimenting, I discovered that the wildcard handling was changed in 2.10.0. I downgraded my container to 2.9.1, and my Caddyfile worked without any problems.
It appears that the wildcard pattern provided in the docs is no longer valid.
After looking through the release notes, I discovered caddyserver/caddy/pull/6959 in which @mholt provides documentation for the change, in particular offering the template for how the wildcard based setup should be handled now.
Please consider updating the docs to prevent other newbies having a similar experience dealing with seemingly outdated documentation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the wildcard pattern documentation page linked in the issue and review caddyserver/caddy/pull/6959 for the 2.10.0 behavior. Update the wildcard certificate example to match the current default handling, then verify that the page no longer recommends the outdated pattern.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100