Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxy content via public-api, even when we're on a simple site. #90895

Merged
merged 3 commits into from
May 24, 2024

Commits on May 23, 2024

  1. Proxy content via public-api, even when we're on a simple site.

    In order to solve #87642, we need to proxy any images in the media area via the public API.
    
    This solves two main cases:
    1) Where the primary redirect is not yet pointed to us via DNS
    2) Where a service like Cloudflare is in front of the primary redirect, and blocks "hotlinking" images
    
    These cases both used to work fine, as media was served from *.files.wordpress.com regardless of the actual
    domain being used.  Once this was been moved to use wp-content/uploads (in order to fix issues when third
    party cookies are blocked), the two cases above (and probably some others we don't know about) stopped working.
    devicenull committed May 23, 2024
    Configuration menu
    Copy the full SHA
    6a9e230 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    29b79c6 View commit details
    Browse the repository at this point in the history

Commits on May 24, 2024

  1. Configuration menu
    Copy the full SHA
    2740d2c View commit details
    Browse the repository at this point in the history