proxy support #829
Nessun revisore
Etichette
Nessuna etichetta
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Nessuna pietra miliare
Nessun progetto
Nessun assegnatario
2 partecipanti
Notifiche
Scadenza
Nessuna scadenza impostata.
Dipendenze
Nessuna dipendenza impostata.
Riferimento: Plume/Plume#829
Caricamento…
Add table
Crea riferimento in una nuova segnalazione
Descrizione non fornita.
Elimina ramo "dr-bonez/Plume:feature/proxy"
L'eliminazione di un ramo è definitiva. Nonostante il ramo eliminato potrebbe continuare ad esistere per un breve periodo di tempo prima di essere realmente eliminato, l'eliminazione NON PUÒ essere annullata in molti casi. Continuare?
Adds support for using a proxy for federation.
Motivation is for being able to support homeservers running as Tor hidden services.
Threading config information into plume-common is the only reason this pr isn't very low impact.
Thank you for pull request and sorry for late reply. But we have less time to review, now. Can you wait for a while, please? Thanks.
Sorry for very late reply.
What need proxy config is only
ClientBuilder
. How about to useCONFIG.proxy()
directly inplume-common/src/activity_pub/mod.rs
?I can't. CONFIG comes from plume-models, which has plume-common as a dependency. Pretty sure you can't have 2 crates that depend on each other.
rebased
Okay, I will merge. Thank you for your work!
Okay, I will merge. Thank you for your work!