Some Content is HTTP2 and Other is HTTP1.1 - This Expected Behavior?

ℹ️ Support
1

Hey All,

I used the excellent guide here:

Install Nextcloud on Ubuntu 24.04 LTS - Complete Guide (mailserverguru.com)

And it seems I’m 99% of the way there. One anomoly is that my http2 seems to only work occasionally with mixed http 1.1 content being displayed in the browser console. Shouldn’t all this reflect h2 for http2?

Here’s an image of what I mean.

Thanks

http2
http2467×510 84.2 KB

2

Anyone happen to know?

3

Hi @theprez1980

Reason of your Issue at the bottom but firs this:

That guide contains some unnecessary steps.

  • Normally it is not necessary to add

      <FilesMatch ".php$">
       SetHandler "proxy:unix:/var/run/php/php8.3-fpm.sock|fcgi://localhost/"
  </FilesMatch>

    to the config like described in point 6 - subpoint 11. That is already done with step

    a2enconf php8.3-fpm

    (point 6, 4)

    That links the file /etc/apache2/conf-available/php8.3-fpm.conf that already contains this lines to /etc/apache2/conf-enabled/php8.3-fpm.conf and all files (linked to) inside /etc/apache2/conf-enabled are automaticaly part of your config.

  • With http2 it is similar: the file /etc/apache2/mods-available/http2.conf is linked to /etc/apache2/mods-enabled/http2.conf
    and this line:

    Protocols h2 h2c http/1.1

    is normaly part of it, so no need to add it somewhere else like described in point 11, subpoint 4 of the guide.

That about your Excelent guide :wink:

The reason why you see http/1.1 for those files:

For all of those http/1.1 files, the response code (200) is grayed out in your screenshot. That means, those are localy cached files (you will see when you click on one of them). Those statuses are from the time they where downloaded.

You should force a new download of those files by Ctrl + Shift + R or Shift + F5 (depending on used Browser)

And then look again in your browser console.

Much and good luck,
ernolf

1 Like
4

Thank you for the detailed reply. I can’t take credit for the guide (I didnt’ make it, but it helped tremendously, and I’ll share the comments with the author.

One last question, in that guide I see this is recommended:

        Options FollowSymLinks MultiViews
        AllowOverride All
        Require all granted
        LimitRequestBody 0

In other guides and help on this forum, this is recommended instead:

Options MultiViews FollowSymlinks

AllowOverride All

Order allow,deny

Allow from all

LimitRequestBody 0

What’s the difference and what do you recommend?

Thanks

5

I don’t see that in the guide.

I only could find

        <Directory /var/www/html/nextcloud>
            Options Indexes FollowSymLinks
            AllowOverride All
            Require all granted
        </Directory>

… and all I can do is shake my head at the nonsense that is being spouted there.
I would strongly advise against using “Indexes” in nextcloud for security reasons!

This is how it should be following the → official manual ← :

<Directory /var/www/nextcloud/>
  Require all granted
  AllowOverride All
  Options FollowSymLinks MultiViews

  <IfModule mod_dav.c>
    Dav off
  </IfModule>
</Directory>

Order allow,deny
Allow from all

is old syntax used in Apache versions prior to 2.4. In Apache 2.4 and later, it has been replaced by the directive Require all granted. So, the old directives are completely redundant and unnecessary. Don’t use them in this context.

LimitRequestBody 0

if uploading very large files is required, setting LimitRequestBody to 0 (unlimited) is appropriate. By default, Apache 2.4.53 and later limit request body sizes to 1 GB, which might be insufficient for some use cases.

ernolf

1 Like
6

Thanks so much, that clears that up.

Thanks again and enjoy the rest of your weekend.

7

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.