Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Custom origin header is not used in Linux desktop app #2316

Closed
1 task done
thoku1 opened this issue Oct 29, 2023 · 3 comments
Closed
1 task done

[BUG] Custom origin header is not used in Linux desktop app #2316

thoku1 opened this issue Oct 29, 2023 · 3 comments

Comments

@thoku1
Copy link

thoku1 commented Oct 29, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Despite of setting a custom origin header, Altair always uses "Origin: electron://altair". Other headers are send correctly.
On a site, which requires setting the original header, I always get a "401 Unauthorized" response. Using curl with same parameters I get the correct results.

Expected Behavior

No response

Steps To Reproduce

  1. Open new tab
  2. Set custom origin header (using environment, global environment or Set Headers menu)
  3. Send a request
  4. Watch proxied traffic, you will always find "Origin: electron://altair".

Environment

- OS:Kali Linux
- Browser:
- Platform: Electron Desktop App
- Version: 5.2.5_x86_64_linux

Additional context

No response

@wickning1
Copy link

Having the same problem on altair_5.2.5_arm64_mac. My first time trying Altair but can't use it because my service demands that host and origin match. :/

@thoku1
Copy link
Author

thoku1 commented Nov 4, 2023

And also on altair_5.2.5_x64_win and Firefox-Addon.

@thoku1
Copy link
Author

thoku1 commented Nov 11, 2023

Fixed in 5.2.6, thanks for your great app and support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants