> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/upload-and-cover-url-validation.md).

# Upload & Cover URL validation

URL inputs cross a trust boundary and require stronger validation than syntactic URL parsing.

## Validation layers

* allow only approved public schemes (normally HTTPS);
* reject credentials embedded in URLs;
* resolve DNS and reject private, loopback, link-local, reserved, or otherwise disallowed destinations;
* revalidate every redirect target;
* cap redirect count;
* enforce request/connect/read timeouts;
* bound maximum content size;
* validate expected content type and actual payload expectations;
* avoid leaking fetched content or sensitive network details into error messages.

The same checks should apply after redirects, not only to the original URL.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/upload-and-cover-url-validation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.