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've got a little trouble using bearer_auth with wasm.
let me explain.
I've set-up a small server with two simple functions that send back a small JSON. The first function accessible without any authentification send back a JWT, the second one needs a JWT.
When I ran some tests from the command line, everything works fine.
The first function gives me a JWT and I'm using it with the second reqwest call using bearer_auth header.
If I do the same thing from a browser, within a Dioxus app, using the same code, the first call without authentification works well, but the second one using bearer_auth always failed with NetworkError when attempting to fetch resource
I think I've missed something, probably simple, but I don't know what.
Fedora 41 / x84_64
rustc 1.83.0 (90b35a623 2024-11-26)
reqwest = { version = "0.12", features = ["json", "brotli"] }
tested on Firefox and Chromium.
The text was updated successfully, but these errors were encountered:
Hi,
I've got a little trouble using bearer_auth with wasm.
let me explain.
I've set-up a small server with two simple functions that send back a small JSON. The first function accessible without any authentification send back a JWT, the second one needs a JWT.
When I ran some tests from the command line, everything works fine.
The first function gives me a JWT and I'm using it with the second reqwest call using bearer_auth header.
If I do the same thing from a browser, within a Dioxus app, using the same code, the first call without authentification works well, but the second one using bearer_auth always failed with NetworkError when attempting to fetch resource
I think I've missed something, probably simple, but I don't know what.
Fedora 41 / x84_64
rustc 1.83.0 (90b35a623 2024-11-26)
reqwest = { version = "0.12", features = ["json", "brotli"] }
tested on Firefox and Chromium.
The text was updated successfully, but these errors were encountered: