Allow specifying default site / vhost

Bug #1863170 reported by Haw Loeung
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Content Cache Charm
Fix Released
Wishlist
Haw Loeung

Bug Description

Hi,

In some cases, we have multiple sites configured, with HAProxy generated config as:

| listen combined-443
| bind 0.0.0.0:443 ssl crt /var/lib/haproxy
| bind :::443 ssl crt /var/lib/haproxy
| use_backend backend-cached-public-apps-stagi-d55df9b if { hdr(Host) -i public.apps.staging.ubuntu.com }
| use_backend backend-cached-storage-staging-s-74077a4 if { hdr(Host) -i storage.staging.snapcraftcontent.com }

We should have an option to specify a default. Or perhaps make the first or last in the defined YAML the default. Or both.

Related branches

Haw Loeung (hloeung)
Changed in content-cache-charm:
importance: Undecided → Wishlist
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: New → Triaged
Revision history for this message
Haw Loeung (hloeung) wrote :

We also want to have a default for sites not yet set up or people hitting the servers by IP. For this, we should have a flag 'default' or similar instead.

Changed in content-cache-charm:
assignee: nobody → Haw Loeung (hloeung)
status: Triaged → In Progress
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: In Progress → Fix Committed
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.