Will Ubuntu 22.04 support HTTP v3?

Discussion in 'Feature Requests' started by concept21, Nov 6, 2022.

  1. concept21

    concept21 Active Member

    I heard that HTTP v3 is great for mobile networks (switching hot spots often). :eek:

    Which new Linux versions will support this? Will ISPConfig v3.2.x support newer Linux version with built-in HTTP v3? :)
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    It isn't dependent on the OS, but on the webserver (nginx/apache2 if you use ISPConfig). Those do not support http3 yet afaik.
    concept21 likes this.
  3. ahrasis

    ahrasis Well-Known Member

    If I am not mistaken, other than web server support, browsers and may be dns servers might be related as well. Cloudflare had it since 2019 and most browsers already supported it.
    budgierless likes this.
  4. remkoh

    remkoh Member

    I'm using OpenLiteSpeed as a reverse proxy in front of my webservers to serve several websites over HTTP3 to the clients.

    Although in my case it's a separate VM, you should be able to implement it on the same host as your ISPConfig installation if you let Apache or Nginx (whichever you use) run on different ports than 80 and 443 with some tweaking of the configs.

    There's no way to configure OpenLiteSpeed from within ISPConfig. You need to do that manually or script it somehow.
    But running it on the same host does give you the advantage to simply use the same certificate files in OpenLiteSpeed that you created with ISPConfig for HTTPS.
  5. ahrasis

    ahrasis Well-Known Member

    ISPConfig does not support dual web server in a host, if that you were trying to say, for the reason that was already mentioned several times in various threads. Logic also dictates that running multiple web servers in a single host will definitely use more resources.

    I have been using http3 since CloudFlare offer it as beta and I don't have to have multiple web server in a single host at all.
  6. remkoh

    remkoh Member

    Are you saying it's mandatory for ISPConfig to function the supported webservers Apache or Nginx need to be running on port 80 and 443 and not for example 8080 and 8443? I find that hard to believe.
    During install ISPConfig is looking for installed binaries to determine if Apache or Nginx is installed, not which port they're running on as far as my experience goes.

    A while back I was playing around with a customized Nginx on a alternate port to test HTTP3 support and when I updated ISPConfig because of a new version it decided to switch from using Apache to Nginx.

    As I said it would need some tweaking. Custom config files for vhost at least when running Apache (which ISPConfig supports).
    And if you're running Nginx maybe not even that as ISPConfig lets you set ports to be used when creating a website.
    After that you should be able to run anything on port 80 and 443.

    Although this is all theoretical I can't see any reason why this wouldn't be possible.
    If I'd had the time I'd gladly make it a test case. But unfortunately I haven't.

    You're absolutely right about that.
    And my guess is you're not only using Cloudflare for it's HTTP3 support. Others can have several reasons to use or not use Cloudflare.
    Last edited: Dec 3, 2022
  7. ahrasis

    ahrasis Well-Known Member

    That was not what I said and you clearly twisted it, and really deviated from it, a lot.

    Anyway, that is your server so do it your own way.
  8. remkoh

    remkoh Member

    I started with a legit question to find an answer on why you say ISPConfig does not support dual web server in a host.
    There was no intention to twist anything.
  9. ahrasis

    ahrasis Well-Known Member

    That is to me a clear twist and real deviation from what I said, because what I said is very much clear and straightforward.

    But your post clearly did, so your question is not at all legit. It is a known fact that ISPConfig does not support dual web server in a host. You can modify or script whatsoever you are capable of to make that works on your own server but, a fact is a fact.
  10. remkoh

    remkoh Member

    The only fact about dual webserver is you need to choose between Apache and Nginx in your base installation as ISPConfig can only manage one and not both.
    Using port 80 and 443 is not mandatory as far as I know.
    Nowhere I made a statement to install both.
    So your statement about no dual webserver, besides you can't have both Apache and Nginx, still remains unclear to me.

    If you tweak the right way to make your base install with ISPConfig run on other ports than 80 and 443 you make use of default ISPConfig capabilities only to configure your websites from within ISPConfig to use the right alternate ports and do only config changes outside ISPConfig that won't interfere with ISPConfig install and update scripts.
    Then you have port 80 and 443 free for OpenLiteSpeed as a reverse proxy.

    I'm not saying everyone should do this. I'm just pointing out a possibility for those who realy realy realy want HTTP3 support within their own system.
    Which by the way I've not implemented myself in this way as I'm lucky enough to have plenty of resources to run OpenLiteSpeed on a separate VM.

Share This Page