Latest Nextcloud X-Frame-Options and Opcache warnings in admin panel

Support
,
6

Do you have an .htaccess.rpmnew in the nextcloud folder?
I had it and replaced the old version with the newer one: no more X-Frame-Options warning.

Checking the http headers before and after the change:

  • With the old file, which contains the X-Frame-Options directive, the response header option was being sent twice and the warning showed up.
  • With the new .htaccess file, only one X-Frame-Options is returned by the http response header, and no warning on Nextcloud’s admin page.

Maybe you are facing the same issue.

To enable opcache we need an additional package:

yum install rh-php56-php-opcache

opcache settings will be located at /etc/opt/rh/rh-php56/php.d/10-opcache.ini

It works either by editing that file with the recommended settings or, otherwise, adding the values to /etc/opt/rh/rh-php56/php-fpm.d/www.conf with the correct format:

php_value[opcache.enable_cli]=1
php_value[opcache.max_accelerated_files]=10000
php_value[opcache.save_comments]=1
php_value[opcache.revalidate_freq]=1

(recommended settings matching default values were omitted.)

After changing any of the files restart the php-fpm service for the changes to be applied:

systemctl restart rh-php56-php-fpm

It does not work on .htaccess or .user.ini as most of the recommended values are system settings (PHP_INI_SYSTEM).

Still don’t know the right way to make the settings available only to a specific virtualhost (eg. nextcloud). But a workaround could be to disable opcache by setting opcache.enable in the .htaccess file of any other virtualhost.

2 Likes