feat: add headers support for mixpanel proxy api calls #833
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.
Introducing Header Support for Mixpanel Proxy Servers
This pull request introduces a feature enabling proxy servers to request custom headers from the application.
Problem:
Currently, when the proxy server URL is set, it makes API calls in a standard manner. However, if the application wishes to include certain headers, such as authentication tokens or device IDs, this isn't possible.
Solution:
This pull request implements a callback mechanism. Before making an API call, the system requests headers and returns the API endpoint and status code. This information can be utilized by the application for tracking or other purposes.
Implementation:
This implementation introduces a new property in the config class called "MixpanelServerCallback". It contains a method named "getHeaders()" which requests any headers to be passed just before the proxy server API call. Once the API call is complete, it returns the API endpoint and status code via "onResponse()".
Benefits:
Enhanced Proxy API Control:
This solution grants the proxy API full control during Mixpanel proxy API calls.