{"version":"2.1.223","anchor":"per-request-baseurl-override-used-for-filestore-transfers","canonical_anchor":"per-request-baseurl-override-used-for-filestore-transfers","heading":"Per-request baseUrl override, used for filestore transfers","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/per-request-baseurl-override-used-for-filestore-transfers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Per-request baseUrl override, used for filestore transfers\n\nFile downloads can now come from a server-supplied host, but only for unauthenticated requests.\n\n**What**\n\nThe internal HTTP helper can take a base URL from the request itself, which the filestore staging path now uses to fetch from a server-supplied host.\n\n**Details**\n\n- the override returns a request-supplied `baseUrl` only when the request is unauthenticated (`auth: \"none\"`) and the host is not \"frame\"\n- the filestore credential response now carries a `filestoreUrl`, passed as `baseUrl` on readFile requests\n- a warning event is emitted when the server sends a URL that is rejected\n\n**Evidence**\n\n`stage_file_filestore_url_rejected`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}