Can I use
?

Upgrade Insecure Requests

- CR

Declare that browsers should transparently upgrade HTTP resources on a website to HTTPS.

Chrome

  1. 4 - 42: Not supported
  2. 43 - 110: Supported
  3. 111: Supported
  4. 112 - 114: Supported

Edge

  1. 12 - 16: Not supported
  2. 17 - 110: Supported
  3. 111: Supported

Safari

  1. 3.1 - 10: Not supported
  2. 10.1 - 16.3: Supported
  3. 16.4: Supported
  4. 16.5 - TP: Supported

Firefox

  1. 2 - 41: Not supported
  2. 42 - 110: Supported
  3. 111: Supported
  4. 112 - 113: Supported

Opera

  1. 9 - 29: Not supported
  2. 30 - 94: Supported
  3. 95: Supported

IE

  1. 5.5 - 10: Not supported
  2. 11: Not supported

Chrome for Android

  1. 111: Supported

Safari on iOS

  1. 3.2 - 10.2: Not supported
  2. 10.3 - 16.3: Supported
  3. 16.4: Supported
  4. 16.5: Supported

Samsung Internet

  1. 4 - 19.0: Supported
  2. 20: Supported

Opera Mini

  1. all: Not supported

Opera Mobile

  1. 10 - 12.1: Not supported
  2. 73: Supported

UC Browser for Android

  1. 13.4: Supported

Android Browser

  1. 2.1 - 4.4.4: Not supported
  2. 111: Supported

Firefox for Android

  1. 110: Supported

QQ Browser

  1. 13.1: Supported

Baidu Browser

  1. 13.18: Supported

KaiOS Browser

  1. 2.5: Supported
  2. 3: Supported

The HTTP header is Content-Security-Policy: upgrade-insecure-requests. Alternatively, the HTML tag is <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">.

Resources:
WebKit feature request bug
MDN Web Docs - Upgrade Insecure Requests
Demo Website