Question Details on http/3 activation and impact of that procedure on web server configuration files

[Bitpalast]

Server operating system version

Alma 8

Plesk version and microupdate number

18.0.71

On an Alma 8 test server that was updated to 18.0.71 I was hoping that I could activate http/3 on a per-domain basis as suggested in the change log. But it seems that the checkbox for it only appears after plesk bin http3_pref --enable -nginx was run on the console. However, that command applies changes to all virtual host configuration files. I am afraid that executing it on a production server with hundreds of domains will cause a significant downtime of several minutes, maybe up to 20 minutes, as we experience it when running "plesk repair web all" as in such a case all web server configuration files are rewritten, then the web servers restarted, and meanwhile websites become unavailable.

I'd prefer a solution where no service interruption is caused on domains that shall not be switched to http/3. Is that even possible? Or will we have to go through the downtime in order to make a selective http/3 per domain possible? What's is the idea behind offering a selective http/3 switch when this requires that first all web server configuration files must be updated. I'd think that offering a selective option is for avoiding exactly that, but not that I first need to have all files modified only to then get to the point where I can deactivate the option on a per-domain basis again.

Maybe I am wrong and the missing http/3 checkbox without prior console command is an error?