POST /api/v1/media stores an image where the panel keeps a page's and answers with the path to send as `featured_image`. Without it the MCP server could create a page but never give it a picture. The file goes through Media::for(), so it is processed, served and pruned like one uploaded in the panel. Two ways in, one per request: a multipart `file`, or JSON with a `url` the API downloads itself. JPEG, PNG, WebP, GIF or AVIF only, decided from the bytes; no SVG, which is a document that can carry script. The URL is fetched from inside the stack's network, so RemoteImage guards it: HTTPS only, every resolved address must be public, the connection is pinned to the checked address with CURLOPT_RESOLVE so a changing DNS answer cannot swap in a private one, redirects are not followed, and the body is read to a ceiling whatever its headers say. Uploading needs permission to write pages. MediaPolicy::create stays false, so the panel gains no free-standing "new file" button. In the MCP server a multipart binary field becomes `<field>_path` over stdio: the server reads the file from the caller's disk and sends it as multipart, instead of the model pushing base64 through its context. Over HTTP the server's disk is not the caller's, so only `body.url` is offered. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
27 lines
625 B
PHP
27 lines
625 B
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
namespace App\Services\Media;
|
|
|
|
/**
|
|
* Every address a hostname resolves to, IPv4 and IPv6.
|
|
*
|
|
* Its own class so the tests can answer for hosts that do not exist, and so
|
|
* `RemoteImage` can refuse a name that points anywhere private before a single
|
|
* byte is requested.
|
|
*/
|
|
class HostResolver
|
|
{
|
|
/**
|
|
* @return array<int, string>
|
|
*/
|
|
public function resolve(string $host): array
|
|
{
|
|
$v4 = gethostbynamel($host) ?: [];
|
|
$v6 = array_column(@dns_get_record($host, DNS_AAAA) ?: [], 'ipv6');
|
|
|
|
return array_values(array_unique([...$v4, ...$v6]));
|
|
}
|
|
}
|