Document the Authorization header for securing HTTP targets - #79
Merged
Conversation
Credentials in the target url are no longer accepted, so the securing page now leads with the Authorization header (bearer, basic or any value), explains where to set it, notes that existing credentials were converted for you, and documents auth_header on the API. The URL encoding section goes with it, the encoding no longer applies.
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
1 participant
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.
Credentials in the target URL are no longer accepted (cloudmailin/web#313), so this page now leads with the Authorization header instead. It covers setting any value (Bearer, Basic, an API key), where to set it in the dashboard, the in-browser basic auth builder, a note that existing URL credentials were converted automatically with the delivered header unchanged, and the
auth_headerAPI field.The URL encoding section is removed since encoding no longer applies once credentials aren't in a URL.
Merge alongside the web PR so the docs and the product agree.