add support for arbitrary proxies #479
No reviewers
Labels
No labels
Android
CS::needs customer feedback
CS::needs follow up
CS::needs on prem installation
CS::waiting
Chrome
Design:: Ready
Design:: in progress
Design::UX
E2EE
Edge
Firefox
GDPR
Iteration 13 IM
Linux
MacOS
Need::Discussion
Need::Steps to reproduce
Need::Upstream fix
Needs:: Planning
Needs::Dev-Team
Needs::More information
Needs::Priority
Needs::Product
Needs::Refinement
Needs::Severity
Priority::1-Critical
Priority::2-Max
Priority::3-Impending
Priority::4-High
Priority::5-Medium
Priority::6-Low
Priority::7-None
Progress::Backlog
Progress::Review
Progress::Started
Progress::Testing
Progress::Triage
Progress::Waiting
Reporter::Sentry
Safari
Target::Community
Target::Customer
Target::Internal
Target::PoC
Target::Security
Team:Customer-Success
Team:Design
Team:Infrastructure
Team:Instant-Messaging
Team:Product
Team:Workflows
Type::Bug
Type::Design
Type::Documentation
Type::Feature
Type::Improvement
Type::Support
Type::Tests
Windows
blocked
blocked-by-spec
cla-signed
conduit
contribution::advanced
contribution::easy
contribution::help needed
from::review
iOS
p::ti-tenant
performance
product::triage
proposal
refactor
release-blocker
s: dart_openapi_codegen
s::Famedly-Patient
s::Org-Directory
s::Passport-Generator
s::Requeuest
s:CRM
s:Famedly-App
s:Famedly-Web
s:Fhiroxide
s:Fhiroxide-cli
s:Fhiroxide-client
s:Fhirs
s:Hedwig
s:LISA
s:Matrix-Dart-SDK
s:Role-Manager
s:Synapse
s:User-Directory
s:WFS-Matrix
s:Workflow Engine
s:dtls
s:famedly-error
s:fcm-shared-isolate
s:matrix-api-lite
s:multiple-tab-detector
s:native-imaging
severity::1
severity::2
severity::3
severity::4
technical-debt
voip
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Matthias/conduit#479
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/proxy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds support for arbitrary proxy configuration. Based on comments from !52.
Examples:
Include vs. Exclude
If include is an empty list, it is assumed to be
["*"]
.If a domain matches both the exclude and include list, the proxy will only be used if it was included because of a more specific rule than it was excluded. In the above example, the proxy would be used for
ordinary.onion
,matrix.myspecial.onion
, but nothello.myspecial.onion
.mentioned in merge request !55
added 112 commits
famedly:master
Compare with previous version
rebased
added 3 commits
famedly:master
Compare with previous version
added 53 commits
famedly:master
Compare with previous version
changed the description
added 18 commits
famedly:master
Compare with previous version
rebased again
added 77 commits
famedly:master
Compare with previous version
and again...
added 13 commits
famedly:master
b2d55160
- add support for arbitrary proxiesf25f61d4
- fix errors introduced by rebaseCompare with previous version
Can you put all of this in a new file instead of database.rs?
Instead of getting the most specific domain you could also just take the first matching domain to make the code simpler. That's okay if it's documented
Do you need this level of complexity?
Looks good. Can you add some documentation on how to use this feature? In the default config (commented out by default) or in a (new?) markdown documentation file (maybe something for "Advanced features"?)
Include and Exclude lists are separate. If there's a url that matches a rule in both lists, this is the most sane way to handle it.
Will do. The body of this PR sufficient?
Yeah, we can merge it if you move it to another file and add documentation
changed this line in version 8 of the diff
changed this line in version 8 of the diff
changed this line in version 8 of the diff
added 1 commit
c53cc03f
- address pr commentsCompare with previous version
resolved all threads
approved this merge request
mentioned in commit
5f6b0c673c