feat: add custom headers support for Komari instances#5
Open
ciallothu wants to merge 28 commits into
Open
Conversation
- Move all Android files to android/ folder - Rewrite iOS app using MVVM and SwiftData - Align iOS features with Android (Server management, Node details, Terminal snippets, Auto-refresh) - Update CI workflows to use dynamic pre-release tags based on branch push
This reverts commit 7cb6b85. Revert
…, and improving error handling
…rd logic from Android
…WebSocket connection, and add Snippet management UI
[codex] Fix iOS WebSSH input capture
[codex] Allow insecure TLS for iOS Komari servers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds support for custom HTTP headers when connecting to Komari instances.
Users can now configure additional headers per instance, which will be attached to requests sent to the configured Komari server. This is useful for deployments protected by reverse proxies, gateway authentication, or access-control services such as Cloudflare Access, without making the feature specific to any single provider.
Motivation
Some Komari deployments are protected behind additional authentication layers. For example, Cloudflare Access requires non-browser clients to include service token headers:
CF-Access-Client-IdCF-Access-Client-SecretPreviously, Yanami could not connect to these protected Komari instances because there was no way to attach custom headers to API requests. By adding generic custom header support, Yanami can work with Cloudflare Access as well as other self-hosted authentication gateways and reverse proxies.
Changes
Example use cases
Notes
This feature does not introduce any provider-specific logic. Cloudflare Access is only one supported use case through the generic custom headers mechanism.