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
I already searched, and this feature request or improvement is not a duplicate.
Feature scope
Improve existing functionality
Feature request related to a problem
Browsers like Chrome don't provide a relative quality factor for the Accept-Encoding header, but use a fixed order, that does not necessarily express the preference of the browser, but is more likely to ensure backwards compatibility with older web servers. The static-web-server however only checks whether a precompressed file exists for the most preferred, i.e. first accepted encoding.
Describe the solution you'd like
Keep the same ordering by quality, but look for precompressed files in all accepted encoding standards.
Describe alternatives you've considered
If no quality order is provided in the header, it might be useful to have the web server choose a quality order, e.g. for precompressed files, based on file size.
Build target
All targets
Additional context
No response
The text was updated successfully, but these errors were encountered:
Browsers like Chrome don't provide a relative quality factor for the Accept-Encoding header, but use a fixed order, that does not necessarily express the preference of the browser, but is more likely to ensure backwards compatibility with older web servers. The static-web-server however only checks whether a precompressed file exists for the most preferred, i.e. first accepted encoding.
Is there any reference from Chrome docs about this behavior that you can share?
How about also other browsers do they behave the same?
Search for duplicate feature request
Feature scope
Improve existing functionality
Feature request related to a problem
Browsers like Chrome don't provide a relative quality factor for the Accept-Encoding header, but use a fixed order, that does not necessarily express the preference of the browser, but is more likely to ensure backwards compatibility with older web servers. The static-web-server however only checks whether a precompressed file exists for the most preferred, i.e. first accepted encoding.
Describe the solution you'd like
Keep the same ordering by quality, but look for precompressed files in all accepted encoding standards.
Describe alternatives you've considered
If no quality order is provided in the header, it might be useful to have the web server choose a quality order, e.g. for precompressed files, based on file size.
Build target
All targets
Additional context
No response
The text was updated successfully, but these errors were encountered: