tauri-apps / tauri-apps/plugins-workspace
[bug] tauri did read http_proxy auto but did not read no_proxy
- Dominant language
- Rust
- Stars
- 1.8k
- Forks
- 602
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 9
Description
### Describe the bug
I am behind a proxy and my OS is Deepin Linux 20.8, I reach internet through http_proxy, but I need to connect intranet services through no_proxy env values.
I build an demo app that need to connect intranet services which one is already registered in no_proxy values. I trigger the request from `tauri-apps/api/http` fetch, but I got status code 503, and if I connect the same service through the browser, it works well, and if I remove the service IP from no_proxy values I get 503 code the same, so it indeed does not read the env no_proxy values.
Meanwhile, when I trigger a request to a internet connection, `tauri-apps/api/http` fetch works well, it means it really read the http_proxy auto.
So I think, `tauri-apps/api/http` read http_proxy auto but did not read no_proxy, this should be a problem.
One more thing is when http_proxy and no_proxy changes, even rebuild from rust side, it does not read the new value, only restart OS, it reads the new values.
### Reproduction
_No response_
### Expected behavior
Should read the http_proxy and no_proxy both ,or did not read them either but expose api to set them.Should read the new value when env value changes.
### Platform and versions
```text
Environment
› OS: Linux 20.8 X64
› Node.js: 14.16.1
› npm: 6.14.12
› pnpm: Not installed!
› yarn: Not installed!
› rustup: 1.25.2
› rustc: 1.67.1
› cargo: 1.67.1
› Rust toolchain: stable-x86_64-unknown-linux-gnu
Packages
› @tauri-apps/cli [NPM]: 1.2.3
› @tauri-apps/api [NPM]: 1.2.0
› tauri [RUST]: 1.2.4,
› tauri-build [RUST]: 1.2.1,
› tao [RUST]: 0.15.8,
› wry [RUST]: 0.23.4,
App
› build-type: bundle
› CSP: unset
› distDir: ../dist
› devPath: http://localhost:1420/
› framework: Vue.js
› bundler: Vite
App directory structure
├─ .git
├─ src-tauri
├─ node_modules
├─ public
├─ src
├─ .vscode
└─ dist
```
### Stack trace
_No response_
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.