[0.1.13] [Linux] Request: Add custom headers to connections
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- desktop
Research direction
Start by locating the connection setup and request handling entry points in the Tether codebase; the issue does not name specific files or tests. Trace how requests to Open WebUI are made and determine where custom headers would need to apply. Done means configured headers are sent with every connection request and the Pangolin protected resource works remotely.
Written by the indexing model from the issue text.
Description
Version
0.1.13
Platform
Linux
Description
I use Pangolin to connect to Open WebUI as a public resource when not at home. However, when attempting to connect from outside my home network using Tether it sits at a blank white screen.
My recommendation would be to add support for custom headers that get sent along with every request. This would allow me to add a shared link and add the P-Access-Token-Id and P-Access-Token headers to my Open WebUI connection authorizing me when remote.
Steps to reproduce
- Run Open WebUI
- Expose it via Pangolin as a Public Resource with authorization turned on
- Attempt to access Open WebUI from a remote network
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 130
- Forks
- 8
- Avg merge
- 1m
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-webui/tether
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
open-webui/tether#52 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
open-webui/tether#51 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
open-webui/tether#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
open-webui/tether#49 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
open-webui/tether#48 ·
Maintainers usually reply within 1 day
All issues in open-webui/tether
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voidzero-dev/void#835 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AykutSarac/jsoncrack.com#616 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melgarafael/DeskcommCRM#4679 ·
Maintainers usually reply within 1 day
-
enhancement size:medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day