You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Followup to #4150, #4151 /cc @ueffel@polarathene
After a bit of discussion with @mholt, we decided to remove `prefer` as a subdirective and just go with using the order implicitly always. Simpler config, simpler docs, etc.
Followup to #4150, #4151 /cc @ueffel@polarathene
After a bit of discussion with @mholt, we decided to remove `prefer` as a subdirective and just go with using the order implicitly always. Simpler config, simpler docs, etc.
Followup to #4150, #4151 /cc @ueffel@polarathene
After a bit of discussion with @mholt, we decided to remove `prefer` as a subdirective and just go with using the order implicitly always. Simpler config, simpler docs, etc.
Effectively changes 7776471 and reverts a small part of f35a7fa.
Creating an issue for a recent discussion on encode directive docs PR for upcoming 2.4 release.
Proposal
For a Caddyfile,
encode.prefer
could be set implicitly.That would be intuitive to the user and consistent with the new
file_server.precompressed
feature.Justification
Without
prefer
, only the first supported client encoding is negotiated (often gzip).Impact of implicit preference:
encode
adopting sane defaults.file_server.precompressed
has implicit preference.zstd
andgzip
are officially supported (50% chancegzip
remains preferred).zstd
officially.gzip
is supported it often took priority, even if unintentional (egcURL
).The text was updated successfully, but these errors were encountered: