{"version":"2.1.239","anchor":"artifact-tool-rejects-a-url-pointing-inside-the-artifact","canonical_anchor":"artifact-tool-rejects-a-url-pointing-inside-the-artifact","heading":"Artifact tool rejects a URL pointing inside the artifact","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/artifact-tool-rejects-a-url-pointing-inside-the-artifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Artifact tool rejects a URL pointing inside the artifact\n\nPointing the artifact tool at a URL inside the artifact now fails with a clear explanation.\n\n**What**\n\nPassing a `url` that names a path inside the artifact now fails with a clear error saying to pass the artifact's own URL instead, on both the live-edit and asset paths. Separately, asset-upload consent is now honoured in cases where an extra negated condition previously skipped it.\n\n**Details**\n\n- The new validation returns errorCode 4.\n- The public-reader failure now carries a distinct `errorCode: \"public_read_disabled\"` alongside its existing message text.\n\n**Evidence**\n\n`names a path inside the artifact`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}