Feature/tiqr add apple api http2 proxy #417
Open
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
We add a seperate front and backend on stepup tiqr servers that also serve as loadbalancer. It allows proxying http/1 requests to the http/2 only Apple API
API. An Haproxy instance is installed on StepupTIQR machines. It's only purpose is to proxy the requests from Tiqr to the Apple Push Notification service (APNs). Since the curl shipped with CentOS7 is http/1 only, and the APNs is http/2 only we use this proxy.
…y setting the boolean apns_http2_proxy to true
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Apple Push Notification service (APNs) only supports http/2. Since curl shipped with CentOS7 only supports http/1 we are not able to send push messages to this Apple API.
We use haproxy to create a simple reverse http proxy between the Apple API and the TIQR application to proxy the requests (since Haproxy understands http/2).
On hosts where the whole stack is installed on 1 machine (and an Haproxy loadbalancer is already present) we add an extra back- and frontend for this purpose. TIQR can simple push the messages to http://localhost:5000