Make WordPress Core

Changes between Initial Version and Version 3 of Ticket #39224


Ignore:
Timestamp:
10/25/2020 03:53:11 AM (15 months ago)
Author:
TimothyBlynJacobs
Comment:

This was fixed when we introduced Application Passwords in #42790.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #39224

    • Property Status changed from new to closed
    • Property Type changed from defect (bug) to enhancement
    • Property Summary changed from Wordpress REST API and Authentication header to Add Authorization header compatibility workaround to default htaccess
    • Property Milestone changed from Awaiting Review to
    • Property Resolution changed from to worksforme
  • Ticket #39224 – Description

    initial v3  
    22As per https://github.com/WP-API/WP-API/issues/2512 this was a known issue but it was decided to take no action - "just configure your server the right way".
    33But I wonder why not fix this issue by updating the default .htaccess to pass through the Authentication header?
    4 The REST API allows a whole new level of interaction with wordpress based websites that was not possible before. However, most Wordpress Users do not even know what .htaccess is! So lacking the hability to make it work by just installing plugins kind of undermines the whole premise of the REST API.
     4The REST API allows a whole new level of interaction with wordpress based websites that was not possible before. However, most WordPress Users do not even know what .htaccess is! So lacking the hability to make it work by just installing plugins kind of undermines the whole premise of the REST API.
    55The fix is described here: https://github.com/WP-API/Basic-Auth/issues/35