feat: AJAX uses token authentication #181
Draft
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.
Related:
@wordpress/api-fetch
utility Automattic/jetpack#45254What?
Authenticate AJAX requests with application passwords send via an authorization
header.
Why?
The GutenbergKit editor does not have authorization cookies, so we must rely
upon a different authorization mechanism.
Ref CMM-713. Close CMM-768.
How?
Set the
Authorization
header viajQuery.ajaxSetup
and by overloading thewindow.wp.ajax
utilities.Testing Instructions
Tip
Test using prototype builds from the sibling PRs:
Note
Selecting media from cloud-based storage providers on Android often fails due to a Chrome bug (CMM-782); use the Browse... menu to select local files.
Accessibility Testing Instructions
N/A, no navigation changes.
Screenshots or screencast
N/A, no visual changes.