Add HTTP Support #13
Open
Add HTTP Support #13
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
Author
|
@DeanCording could you take a look at this PR and provide feedback? |
Owner
|
Thanks @vkhurana, I'm working on the API 2.0 version at the moment and will incorporate the HTTP support with it. |
Author
|
That sounds good @DeanCording, by when do you think that'll be done? If 2.0 is far out, maybe we can merge this for now, to unblock others too? |
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.
This is useful for when you have nodered behind a ssl terminating reverse proxy, such as traefik, or nginx.
There's a new UI option for selecting 'protocol' (http or https). When https is selected, the cert and key text boxes are visible, and they are hidden when http is selected, since they're not relevant for http.
Fixes issue #11