[wp-trac] [WordPress Trac] #40020: Customizer fails to load in Safari due to X-Origin Header mismatch

[WordPress Trac]

#40020: Customizer fails to load in Safari due to X-Origin Header mismatch
-------------------------------+------------------------------
 Reporter:  nickkeenan         |       Owner:
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Customize          |     Version:  4.7.2
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by westonruter):

 Replying to [comment:4 endortrails]:
 > 4. NGINX with a single add_header X-Frame-Options SAMEORIGIN; set in
 configs.

 So if you remove this Nginx rule, the Customizer loads as expected in
 Safari?

 The resolution here may be that the Nginx config should be removed in
 favor of adding the `X-Frame-Options` header via PHP in WordPress only.

 > 2. WordPress network using subdomains
 > 3. Wildcard SSL cert to secure all subdomains

 To confirm, the `home` and `siteurl` on each of the sites match each
 other, right?

 Related: #38571

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40020#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform