- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 546 for customer (0.04 sec)
-
tests/test_sub_callbacks.py
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sat Dec 27 18:19:10 UTC 2025 - 12.9K bytes - Viewed (0) -
docs/site-replication/run-ssec-object-replication.sh
src_obj1_etag=$(echo "${stat_out1}" | jq '.etag') src_obj1_size=$(echo "${stat_out1}" | jq '.size') src_obj1_md5=$(echo "${stat_out1}" | jq '.metadata."X-Amz-Server-Side-Encryption-Customer-Key-Md5"') echo "Stat minio1/test-bucket/defpartsize" ./mc stat --no-list minio1/test-bucket/defpartsize --enc-c "minio1/test-bucket/defpartsize=${TEST_MINIO_ENC_KEY}" --insecure --jsonRegistered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Sep 24 08:03:58 UTC 2024 - 9.9K bytes - Viewed (0) -
tests/test_tutorial/test_openapi_callbacks/test_tutorial001.py
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sat Dec 27 18:19:10 UTC 2025 - 8.6K bytes - Viewed (0) -
internal/http/headers.go
AmzServerSideEncryptionCustomerAlgorithm = AmzServerSideEncryption + "-Customer-Algorithm" AmzServerSideEncryptionCustomerKey = AmzServerSideEncryption + "-Customer-Key" AmzServerSideEncryptionCustomerKeyMD5 = AmzServerSideEncryption + "-Customer-Key-Md5" AmzServerSideEncryptionCopyCustomerAlgorithm = "X-Amz-Copy-Source-Server-Side-Encryption-Customer-Algorithm"
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed May 07 15:37:12 UTC 2025 - 10.8K bytes - Viewed (0) -
docs/site-replication/run-ssec-object-replication-with-compression.sh
src_obj1_etag=$(echo "${stat_out1}" | jq '.etag') src_obj1_size=$(echo "${stat_out1}" | jq '.size') src_obj1_md5=$(echo "${stat_out1}" | jq '.metadata."X-Amz-Server-Side-Encryption-Customer-Key-Md5"') echo "Stat minio1/test-bucket/defpartsize" ./mc stat --no-list minio1/test-bucket/defpartsize --enc-c "minio1/test-bucket/defpartsize=${TEST_MINIO_ENC_KEY}" --insecure --jsonRegistered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Sep 24 08:03:58 UTC 2024 - 8.3K bytes - Viewed (0) -
internal/crypto/error.go
ErrMissingCustomerKey = Errorf("The SSE-C request is missing the customer key") // ErrMissingCustomerKeyMD5 indicates that the HTTP headers contains no SSE-C client key // MD5 checksum. ErrMissingCustomerKeyMD5 = Errorf("The SSE-C request is missing the customer key MD5") // ErrInvalidCustomerKey indicates that the SSE-C client key is not valid - e.g. not a
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 4.4K bytes - Viewed (0) -
docs_src/openapi_callbacks/tutorial001_py310.py
from fastapi import APIRouter, FastAPI from pydantic import BaseModel, HttpUrl app = FastAPI() class Invoice(BaseModel): id: str title: str | None = None customer: str total: float class InvoiceEvent(BaseModel): description: str paid: bool class InvoiceEventReceived(BaseModel): ok: bool invoices_callback_router = APIRouter() @invoices_callback_router.post(
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 10 08:55:32 UTC 2025 - 1.3K bytes - Viewed (0) -
docs/ru/docs/advanced/openapi-callbacks.md
Давайте рассмотрим это на примере. Представьте, что вы разрабатываете приложение, позволяющее создавать счета. Эти счета будут иметь `id`, `title` (необязательный), `customer` и `total`. Пользователь вашего API (внешний разработчик) создаст счет в вашем API с помощью POST-запроса. Затем ваш API (предположим) сделает следующее: * Отправит счет клиенту внешнего разработчика.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Thu Dec 11 21:25:03 UTC 2025 - 12.7K bytes - Viewed (0) -
docs/en/docs/advanced/openapi-callbacks.md
Imagine you develop an app that allows creating invoices. These invoices will have an `id`, `title` (optional), `customer`, and `total`. The user of your API (an external developer) will create an invoice in your API with a POST request. Then your API will (let's imagine): * Send the invoice to some customer of the external developer. * Collect the money. * Send a notification back to the API user (the external developer).
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 10 08:55:32 UTC 2025 - 8K bytes - Viewed (0) -
docs/de/docs/advanced/openapi-callbacks.md
Sehen wir uns das alles anhand eines Beispiels an. Stellen Sie sich vor, Sie entwickeln eine Anwendung, mit der Sie Rechnungen erstellen können. Diese Rechnungen haben eine `id`, einen optionalen `title`, einen `customer` (Kunde) und ein `total` (Gesamtsumme). Der Benutzer Ihrer API (ein externer Entwickler) erstellt mit einem POST-Request eine Rechnung in Ihrer API. Dann wird Ihre API (stellen wir uns vor):
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 10 13:54:34 UTC 2025 - 9.2K bytes - Viewed (0)