We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
When restarting or reloading NGINX i'm getting the followin warning:
nginx: [warn] duplicate MIME type "text/html" in /etc/nginx/nginx.d/999-brotli.conf:27
My Brotli config:
brotli on; brotli_comp_level 6; brotli_static on; brotli_types application/atom+xml application/javascript application/json application/rss+xml application/vnd.ms-fontobject application/x-font-opentype application/x-font-truetype application/x-font-ttf application/x-javascript application/xhtml+xml application/xml font/eot font/opentype font/otf font/truetype image/svg+xml image/vnd.microsoft.icon image/x-icon image/x-win-bitmap text/css text/javascript text/plain text/html text/xm
l;
It seems it's being caused by: gzip_types text/plain text/css text/xml text/javascript application/x-javascript application/xml application/javascript;
It's strange because they are both under a different nginx directive.
The text was updated successfully, but these errors were encountered:
Hello @rodehoed
I know that text/html is always compressed by gzip module, this seems to be the same for the ngx_brotli module. And that seems logical.
Please try your brotli.conf without the line text/html
text/html
Sorry, something went wrong.
No branches or pull requests
Hi,
When restarting or reloading NGINX i'm getting the followin warning:
nginx: [warn] duplicate MIME type "text/html" in /etc/nginx/nginx.d/999-brotli.conf:27
My Brotli config:
l;
It seems it's being caused by:
gzip_types text/plain text/css text/xml text/javascript application/x-javascript application/xml application/javascript;
It's strange because they are both under a different nginx directive.
The text was updated successfully, but these errors were encountered: