Fetch can't decompress brotli response

[petrvecera]

I have API which returns JSON data in only br encoding. When I visit the url inside the browser it works well (as well with any other code.

When I try to fetch the data like this:

import { fetch, ResponseType } from "@tauri-apps/api/http"

...
    response = await fetch(url, {
      method: "GET",
      headers: {
        "Accept-Encoding": "br",
        "Accept": "application/json",
      },
      responseType: ResponseType.Binary // this stops it from crashing 
    });


    console.log("Decoded data:", response.data );

it crashes unless I put there the binary

I have tried adding into cargo.toml:

reqwest = { version = "=0.12.18", features = ["json", "multipart", "brotli", "gzip"] }

but it didn't help 🤔 I have found this #7852 where they had problems with gzip ...

I am on Tauri 1

tauri = { version = "=1.8.2", features = [ "process-all", "window-all", "path-all", "dialog-all", "shell-open", "clipboard-write-text", "http-all", "fs-all", "updater"] }

"@tauri-apps/api": "1.6.0",

Any ideas what could be wrong?

[petrvecera]

I was able to fix this with downgrading the reqwest - so I assume there has to be some kind of bug:

reqwest = { version = "=0.11", features = ["json", "multipart", "brotli", "gzip", "blocking"] }

[FabianLars]

nope, tauri v1 is just stuck with reqwest 0.11.
what you added there is supposed to overwrite the features of the reqwest version that tauri uses (cargo combines all feature flags of a dependency when it was declared multiple times).

[petrvecera]

Hmm, I tried adding just ["json", "multipart", "brotli", "gzip", "blocking"] and I saw that it "rebuild" deps and it still didn't work. Only when I downgraded it to 0.11 it started working. But I saw that it installed reqwest in 2 versions. So I assume it installed 0.12 added those features but the system still used 0.11 which didn't use those features.

Hmm we have deps defined like this and we use dependabot which is trying to update everything. However what you are saying tauri has some of those deps locked. Do you have any docs describing this behaviour and which deps are locked? Although you are saying that it combines the features flags - it might be confusing for us to think it's using some new version instead of the old one 🤔

Thank you very much 🙏

[dependencies]
keyring = "=2.3.3"
log = "=0.4.22"
machine-uid = "=0.5.3"
nom = "=7.1.3"
notify = "=6.1.1"
oauth2 = "=4.4.2"
regex = "=1.11.1"
reqwest = { version = "=0.12.12", features = ["json", "multipart"] }
rev_lines = "=0.3.0"
serde_json = "=1.0.137"
serde = { version = "=1.0.216", features = ["derive"] }
tauri = { version = "=1.8.2", features = [ "process-all", "window-all", "path-all", "dialog-all", "shell-open", "clipboard-write-text", "http-all", "fs-all", "updater"] }
tauri-plugin-deep-link = "=0.1.2"
tauri-plugin-fs-watch = { git = "https://github.com/tauri-apps/plugins-workspace", branch = "dev" }
tauri-plugin-log = { git = "https://github.com/tauri-apps/plugins-workspace", branch = "dev" }
tauri-plugin-single-instance = { git = "https://github.com/tauri-apps/plugins-workspace", branch = "dev" }
tauri-plugin-store = { git = "https://github.com/tauri-apps/plugins-workspace", branch = "dev" }
tauri-plugin-window-state = "=0.1.1"
thiserror = "=1.0.69"
tokio = { version = "=1.43.0", features = ["time"] }
vault = "=8.0.1"
window-shadows = "=0.2.2"
# monitoring by sentry
sentry = "=0.34.0"
# For the OBS interface we need to expose webserver
tiny_http = "=0.12.0"

[FabianLars]

Tauri itself depends on reqwest 0.11 == it has it in its own cargo.toml file.

0.11 vs 0.12 are like 1.0 vs 2.0 so not semver compatible (in other words, they count as completely different packages) which means that cargo will not combine them.

Tauri doesn't "lock" any of its dependencies outside of this semver behavior.