security.input_url_refused

A URL in the request was refused


Type	`https://mthds.ai/errors/security.input_url_refused`
Family	`security`: Refusals made for safety. An implementation may also record each one as a security event.
Domain	`input`: the caller acts, by changing the request or its inputs
Retry	`no`: repeating the operation fails the same way
HTTP status	`422`
Raised as	a problem document, sent as the body of an HTTP response or kept in a run's record

What it means

A URL the caller supplied points somewhere a security rule forbids the runtime to fetch, such as a private address.

What to do

Send a URL that resolves to the public internet over https, or send the file's content itself.

Next steps

A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, the caller, and the second for any other reader.

Reader	Kind	Detail
The domain's actor	`change_input`	Give the input '`{input}`' a URL on the public internet, or send the file itself, then send the request again.
Any other reader	`change_input`	Pass this to the caller, whose input '`{input}`' names a URL a security rule forbids.

Detail

The problem's detail is written from this template, filled with the occurrence's parameters:

The URL of the input '{input}' points at a {target_class} target, which a security rule forbids (reason: {reason}).

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`input`	`identifier`	The input whose URL was refused.
`target_class`	one of `loopback`, `private`, `link_local`, `metadata`, `scheme`	Where the URL points: a loopback, private or link-local address, a cloud metadata service, or a scheme the runtime does not fetch.
`reason`	`identifier`	The rule that refused it.