- Sort Score
- Result 10 results
- Languages All
Results 531 - 540 of 1,562 for example (0.07 sec)
-
docs/pt/docs/advanced/behind-a-proxy.md
// Mais coisas aqui "servers": [ { "url": "/api/v1" }, { "url": "https://stag.example.com", "description": "Staging environment" }, { "url": "https://prod.example.com", "description": "Production environment" } ], "paths": { // Mais coisas aqui } } ```
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 27 15:28:18 UTC 2024 - 12.2K bytes - Viewed (0) -
SECURITY.md
If you think you found a vulnerability, and even if you are not sure about it, please report it right away by sending an email to: ******@****.***. Please try to be as explicit as possible, describing all the steps and example code to reproduce the security issue. I (the author, [@tiangolo](https://twitter.com/tiangolo)) will review it thoroughly and get back to you. ## Public Discussions
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Sep 11 16:15:49 UTC 2022 - 1.3K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/connection/FailedPlan.kt
* to use `H2_PRIOR_KNOWLEDGE` but the URL's scheme is `https:`. * * Preemptive proxy authentication failed. * * Planning failures are not necessarily fatal. For example, even if we can't DNS lookup the first * proxy in a list, looking up a subsequent one may succeed. */ internal class FailedPlan(e: Throwable) : RoutePlanner.Plan {
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Wed Dec 20 23:27:07 UTC 2023 - 1.5K bytes - Viewed (0) -
helm-releases/minio-3.0.0.tgz
ip-name: "" # nginx.ingress.kubernetes.io/secure-backends: "true" # nginx.ingress.kubernetes.io/backend-protocol: "HTTPS" # nginx.ingress.kubernetes.io/whitelist-source-range: 0.0.0.0/0 path: / hosts: - chart-example.local tls: [] # - secretName: chart-example-tls # hosts: # - chart-example.local consoleService: type: ClusterIP clusterIP: ~ ## Make sure to match it to minioConsolePort port: "9001" nodePort: 32001 consoleIngress: enabled: false labels: {} # node-role.kubernetes.io/ingress: platform...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 02 01:47:43 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-3.1.3.tgz
ip-name: "" # nginx.ingress.kubernetes.io/secure-backends: "true" # nginx.ingress.kubernetes.io/backend-protocol: "HTTPS" # nginx.ingress.kubernetes.io/whitelist-source-range: 0.0.0.0/0 path: / hosts: - chart-example.local tls: [] # - secretName: chart-example-tls # hosts: # - chart-example.local consoleService: type: ClusterIP clusterIP: ~ ## Make sure to match it to minioConsolePort port: "9001" nodePort: 32001 consoleIngress: enabled: false labels: {} # node-role.kubernetes.io/ingress: platform...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Sep 18 18:09:59 UTC 2021 - 14.4K bytes - Viewed (0) -
internal/disk/fdatasync_linux.go
) // Fdatasync - fdatasync() is similar to fsync(), but does not flush modified metadata // unless that metadata is needed in order to allow a subsequent data retrieval // to be correctly handled. For example, changes to st_atime or st_mtime // (respectively, time of last access and time of last modification; see inode(7)) // do not require flushing because they are not necessary for a subsequent data
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Sep 29 23:40:28 UTC 2021 - 1.8K bytes - Viewed (0) -
docs/ja/docs/tutorial/security/first-steps.md
{!../../docs_src/security/tutorial001.py!} ``` /// tip | "豆知識" ここで、`tokenUrl="token"`は、まだ作成していない相対URL`token`を指します。相対URLなので、`./token`と同じです。 相対URLを使っているので、APIが`https://example.com/`にある場合、`https://example.com/token`を参照します。しかし、APIが`https://example.com/api/v1/`にある場合は`https://example.com/api/v1/token`を参照することになります。 相対 URL を使うことは、[プロキシと接続](../../advanced/behind-a-proxy.md){.internal-link target=_blank}のような高度なユースケースでもアプリケーションを動作させ続けるために重要です。 ///
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 10.5K bytes - Viewed (0) -
architecture/ambient/ztunnel.md
* This includes UDP, non-compliant HTTP, server-first protocols, stateful sets, external services, etc. * Explicitly opting into behavioral changes can be acceptable. For example, introducing Istio multi-cluster semantics. * Ensure traffic between mesh workloads is securely encrypted with an Istio identity. * Be lightweight enough to not limit adoption.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Jul 17 23:10:17 UTC 2024 - 16.8K bytes - Viewed (0) -
dbflute_fess/dfprop/conditionBeanMap.dfprop
# , (and prefix '!' means excluding, '%' means reviving) # table: table name (hint) or $$ALL$$ # column: column name (hint) or $$CommonColumn$$ or $$VersionNo$$ # # Example: # map:{ # # This means that String includes GreaterThan at MEMBER.MEMBER_ACCOUNT only # # and LessThan at PRODUCT.PRODUCT_NAME and PRODUCT.PRODUCT_HANDLE_CODE,
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Sat Oct 31 23:35:14 UTC 2015 - 4K bytes - Viewed (0) -
docs/pt/docs/tutorial/handling-errors.md
Neste exemplo, quando o cliente pede, na requisição, por um item cujo ID não existe, a exceção com o status code `404` é lançada: ```Python hl_lines="11" {!../../docs_src/handling_errors/tutorial001.py!} ``` ### A response resultante
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 10K bytes - Viewed (0)