3.1 - 17.4: Not supported 17.5: Not supported 17.6 - TP: Not supported Firefox 2 - 125: Not supported 126 - 127: Supported 128: Supported 129 - 131: Supported Opera 9 - 108: Not supported 109 - 110: Supported 111: Supported
The Content-Encoding header should be "zstd". Complementary information No response Build target Docker linux/amd64 Environment and specs static-web-server:v2.31.1 Rust:v1.78.0 OS:Docker on Ubuntu 22.04 Arch:x86_64 (64-bit) Docker:26.1.3-1 ...
This PR fixes an issue when performing file requests with theAccept-Encoding: zstdheader and getting an incorrectContent-Encodingheader value for Zstd files if enabling thecompression-staticfeature. Then incorrectContent-Encodingheader value waszst(extension) rather thanzstd(encoding). Related Issue Fixes...
Search for "#edge-enable-zsdch-content-encoding". Set the value for the feature to "Disabled". Restart Edge to have the change take effect. Run the scenario that encountered an issue to determine if it still occurs or is resolved.
blob.upload_from_string(archive)# Update headersblob.content_type ="application/json"blob.content_encoding ="zstd"blob.patch() logger.info("Uploaded {} on {}".format(path, bucket))# Trigger ingestion on backendgcp_ingest(repository, revision, platform, suite)returnblob ...
Search for "#edge-enable-zsdch-content-encoding". Set the value for the feature to "Disabled". Restart Edge to have the change take effect. Run the scenario that encountered an issue to determine if it still occurs or is resolved.
private static final String CONTENT_TYPE_CHARSET_ATTRIBUTE = "charset="; private static final String CONTENT_TYPE_BOUNDARY_ATTRIBUTE = "boundary="; private static final String BROTLY_ACCEPT_ENCODING_SUFFIX = ", br"; private static final String ZSTD_ACCEPT_ENCODING_SUFFIX = ", zstd"; private Ht...
headers['Content-Encoding'] = 'application/zstd' }const response = await fetch('https://2sq625b43mykl2tqumoue7j4k40vkupj.lambda-url.us-west-2.on.aws', { body: JSON.stringify(contentBlockingRules), headers: { 'Content-Type': 'application/json' ...
If the server wants to use ZSDCH for future responses, it provides the typical response with a non-ZSDCH Content-Encoding but with an extra "get-dictionary" response header. This header provides a pointer to a location for the browser to fetch a ZSDCH dictionary for future use. ...
Search for "#edge-enable-zsdch-content-encoding". Set the value for the feature to "Disabled". Restart Edge to have the change take effect. Run the scenario that encountered an issue to determine if it still occurs or is resolved.