This repository has been archived by the owner on Apr 29, 2021. It is now read-only.
[WIP] #3 QuickConnect support #4
Open
Conversation
This file contains 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
added 10 commits
April 21, 2018 23:26
…nd checks that the real thing does.
- Move pingpong into the regular rest API area, since it's for talking to DSMs. - Move quickconnection API calls out from regular rest API area, since they're for talking to the quickconnect nameservers. - Allow all API requests to take a referer, which is necessary for at least some quickconnect tunnel responses. - Rename/restructure the quickconnect files a bit. - Add method to construct referrer from quickconnect ID.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #3.
Time frame: not for a while; reversing this protocol is a pain.
Progress:
encryption.cgiand some more-intense reverse-engineering)ApiClientto use quickconnectOpen questions: