AcidBurn

For the sake of completeness I will also mention that the updated Helm chart is now also available:

  ingress-nginx: 4.12.1

Looks like the container images for both versions are now available:

  registry.k8s.io/ingress-nginx/controller:v1.12.1  
  registry.k8s.io/ingress-nginx/controller:v1.11.5

The Helm chart has not been updated yet, but it looks like you can use the new container images by manually specifying the updated image tag in the values file:

  controller:  
    image:  
      tag: "v1.12.1"

Resolved in ingress-nginx v1.11.5/v1.12.1 neither of which seem to have been released yet.

I believe HTTP has had this feature since 1999 as the Accept-Language header defined in the HTTP/1.1 RFC[0].

As for why it does not get used, MDN suggests[1] it's because changing it may lead to fingerprinting but there are likely other historical reasons.

[0]: https://datatracker.ietf.org/doc/html/rfc2616#section-14.4

[1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Ac...

I recently started self hosting calibre-web[0] which consumes a calibre database and provides a basic web interface for viewing and uploading books to it. The killer feature for me is that it can act as a Kobo sync server. It makes getting my entire library onto my e-reader a breeze.

0: https://github.com/janeczku/calibre-web

Other than Amazon Certificate Manager as moatra mentions (which I don't think let's you export the certificate), I don't think there is currently an option for free wildcard certificates.

As an alternative you could incorporate provisioning of a Let's Encrypt certificate for the new subdomain into your deployment process since the process is designed to be automated.

Will this work for syncing configuration between two computers running different OSes (Ubuntu and Windows)?