# Page Not Found

The URL `docs/spring_ad00_b828_c815_b9ac/executable_jar_c6f9_ac1c_bc1c_bc0f_bc30_d3ec` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Spring Executable jar 웹 개발 및 배포](https://docs.ocha.ng/spring_ad00_b828_c815_b9ac/executable_jar_c6f9_ac1c_bc1c_bc0f_bc30_d3ec.md)
- [Spring Boot Font 배포 에러](https://docs.ocha.ng/spring_ad00_b828_c815_b9ac/spring_boot_font_bc30_d3ec_c5d0_b7ec.md)
- [Tobi 강연](https://docs.ocha.ng/spring_ad00_b828_c815_b9ac/spring-webflux/tobi-ac15-c5f0.md)
- [Spring Bean init, destroy 순서](https://docs.ocha.ng/spring_ad00_b828_c815_b9ac/bean_init-_destroy_c21c_c11c.md)
- [Spring AOP로 모든 Request 로그 남기기](https://docs.ocha.ng/spring_ad00_b828_c815_b9ac/aop/baa8-b4e0-c6f9-c694-ccad-c5d0-b300-d574-c11c-b85c-adf8-b85c-b0a8-ae30-ae30.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.ocha.ng/spring_ad00_b828_c815_b9ac/executable_jar_c6f9_ac1c_bc1c_bc0f_bc30_d3ec.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.ocha.ng/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.ocha.ng/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/spring_ad00_b828_c815_b9ac/executable_jar_c6f9_ac1c_bc1c_bc0f_bc30_d3ec.md`).

You may also use `Accept: text/markdown` header for content negotiation.