feat: show subscription traffic and expiration - #6061
Open
tianrking wants to merge 1 commit into
Open
Conversation
Contributor
|
Is this something only one specific provider does, or is it some sort of standard all of them follow? |
Author
|
It is the widely used |
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
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.
Closes #6045
Expose subscription usage and expiration metadata from the standard
subscription-userinforesponse header. The update path now keeps response headers through redirects, persists upload/download/total/expiration values with the subscription, and renders a traffic progress bar plus expiration timestamp in the subscription list when the provider supplies the metadata. Providers that do not send the header retain the existing behavior and hide the optional fields.Validation:
git diff --check