Update secured-signal-api to API Gateway#786
Draft
CodeShellDev wants to merge 1 commit intobbernhard:masterfrom
Draft
Update secured-signal-api to API Gateway#786CodeShellDev wants to merge 1 commit intobbernhard:masterfrom
CodeShellDev wants to merge 1 commit intobbernhard:masterfrom
Conversation
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
1 participant
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.
Hey there!
I have just noticed that secured-signal-api isn‘t really a reverse proxy, since it doesn‘t handle SSL and just manages access and unifies data mappings for the API.
Therefor I have changed the description in the README.
Before merging I will have to do some rebranding on my part, but I will mark it as ready-to-review as soon as that happens!