[wp-meta] [Making WordPress.org] #1756: Inconsistent and missing CORS headers on plugin/theme API

[Making WordPress.org]

#1756: Inconsistent and missing CORS headers on plugin/theme API
---------------------------+------------------
 Reporter:  DavidAnderson  |       Owner:
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  API            |  Resolution:
 Keywords:                 |
---------------------------+------------------

Comment (by dd32):

 Replying to [comment:1 obenland]:
 > @dd32 is the missing `Access-Control-Allow-Origin: *` an oversight or on
 purpose, based on the different versions?

 No reason, they were just built at different times for different purposes.
 All WordPress.org API's are written primarily for the use-case at hand,
 they're intentionally not designed to cater to all audiences as they're
 not general-purpose APIs.

 I don't see any harm in adding the extra CORS headers to the 1.0/*.json
 api.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1756#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org