// This operation is useful to determine if a bucket exists.
// The operation returns a 200 OK if the bucket exists and you
// have permission to access it. Otherwise, the operation might
// return responses such as 404 Not Found and 403 Forbidden.
func (api objectAPIHandlers) HeadBucketHandler(w http.ResponseWriter, r *http.Request) {
	ctx := newContext(r, w, "HeadBucket")

	defer logger.AuditLog(ctx, w, r, mustGetClaimsFromToken(r))

    Nullability was previously ambiguous and lenient but now the compiler will
    enforce strict null checks.

 *  New: The response message is now non-null. This is the "Not Found" in the
    status line "HTTP 404 Not Found". If you are building responses
    programmatically (with `new Response.Builder()`) you must now always supply
    a message. An empty string `""` is permitted. This value was never null on

            }
        }
        final int serverLength = server.length;
        final byte[] targetInfo = new byte[(domainLength > 0 ? domainLength + 4 : 0) + (serverLength > 0 ? serverLength + 4 : 0) + 4];
        int offset = 0;
        if (domainLength > 0) {
            writeUShort(targetInfo, offset, 2);
            offset += 2;
            writeUShort(targetInfo, offset, domainLength);
            offset += 2;

crawler.ignore.robots.tags=false
# Whether to ignore content exceptions during crawling.
crawler.ignore.content.exception=true
# HTTP status codes considered as failure URLs.
crawler.failure.url.status.codes=404
# Interval (seconds) for system monitor during crawling.
crawler.system.monitor.interval=60
# Whether to ignore idle threads in hot thread monitoring.
crawler.hotthread.ignore_idle_threads=true

		// of an object to check for object existence. For versioned buckets, MinIO's non-recursive
		// call will report top level prefixes in deleted state, whereas spark/hadoop interpret this as non-empty
		// and throw a 404 exception. This is especially a problem for spark jobs overwriting the same partition
		// repeatedly. This workaround recursively lists the top 3 entries including delete markers to reflect the

- Resolves a potential issue with GC and NS controllers which may delete objects after getting a 404 response from the server during its startup. This PR ensures that requests to aggregated APIs will get 503, not 404 while the APIServiceRegistrationController hasn't finished its job. ([#104748](https://github.com/kubernetes/kubernetes/pull/104748), [@p0lyn0mial](https://github.com/p0lyn0mial))

/// tip | Подсказка

Эта последняя операция пути будет иметь комбинацию тегов: `["items", "custom"]`.

И в документации у неё будут оба ответа: один для `404` и один для `403`.

///

## Модуль main в `FastAPI` { #the-main-fastapi }

Теперь давайте посмотрим на модуль `app/main.py`.

Именно сюда вы импортируете и именно здесь вы используете класс `FastAPI`.

    /** The key of the configuration. e.g. true */
    String CRAWLER_IGNORE_CONTENT_EXCEPTION = "crawler.ignore.content.exception";

    /** The key of the configuration. e.g. 404 */
    String CRAWLER_FAILURE_URL_STATUS_CODES = "crawler.failure.url.status.codes";

    /** The key of the configuration. e.g. 60 */
    String CRAWLER_SYSTEM_MONITOR_INTERVAL = "crawler.system.monitor.interval";

/// tip | Порада

Остання операція шляху матиме комбінацію міток: `["items", "custom"]`.

І вона також матиме в документації обидві відповіді: одну для `404` і одну для `403`.

///

## Основний `FastAPI` { #the-main-fastapi }

Тепер розгляньмо модуль `app/main.py`.

Тут ви імпортуєте і використовуєте клас `FastAPI`.

{* ../../docs_src/bigger_applications/app_an_py310/routers/items.py hl[30:31] title["app/routers/items.py"] *}

/// tip | 提示

這最後一個路徑操作會有組合後的標籤：`["items", "custom"]`。

而且在文件中同時會有 `404` 與 `403` 兩種回應。

///

## 主程式 `FastAPI` { #the-main-fastapi }

現在，來看看 `app/main.py` 這個模組。

你會在這裡匯入並使用 `FastAPI` 類別。

這會是你的應用程式中把一切串起來的主檔案。

而隨著大多數的邏輯都放在各自的模組中，主檔案會相當簡潔。