Search Options

Results per page
Sort
Preferred Languages
Advance

Results 531 - 540 of 1,560 for Example (0.06 sec)

  1. helm-releases/minio-3.5.4.tgz

    writeexamplepolicy policy grants creation or deletion of buckets with name ## starting with example. In addition, grants objects write permissions on buckets starting with ## example. # - name: writeexamplepolicy # statements: # - resources: # - 'arn:aws:s3:::example*/*' # actions: # - "s3:AbortMultipartUpload" # - "s3:GetObject" # - "s3:DeleteObject" # - "s3:PutObject" # - "s3:ListMultipartUploadP" # - resources: # - 'arn:aws:s3:::example*' # actions: # - "s3:CreateBucket" # - "s3:DeleteBucket" # - "s3:GetBucketLocation"...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Mon Feb 14 06:04:53 UTC 2022
    - 17.2K bytes
    - Viewed (0)
  2. helm-releases/minio-3.5.5.tgz

    writeexamplepolicy policy grants creation or deletion of buckets with name ## starting with example. In addition, grants objects write permissions on buckets starting with ## example. # - name: writeexamplepolicy # statements: # - resources: # - 'arn:aws:s3:::example*/*' # actions: # - "s3:AbortMultipartUpload" # - "s3:GetObject" # - "s3:DeleteObject" # - "s3:PutObject" # - "s3:ListMultipartUploadP" # - resources: # - 'arn:aws:s3:::example*' # actions: # - "s3:CreateBucket" # - "s3:DeleteBucket" # - "s3:GetBucketLocation"...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Feb 16 19:44:53 UTC 2022
    - 17.2K bytes
    - Viewed (0)
  3. android/guava/src/com/google/common/collect/Sets.java

       * Creates an empty {@code Set} that uses identity to determine equality. It compares object
       * references, instead of calling {@code equals}, to determine whether a provided object matches
       * an element in the set. For example, {@code contains} returns {@code false} when passed an
       * object that equals a set member, but isn't the same instance. This behavior is similar to the
       * way {@code IdentityHashMap} handles key lookups.
       *
    Registered: Fri Nov 01 12:43:10 UTC 2024
    - Last Modified: Mon Oct 21 14:28:19 UTC 2024
    - 78.8K bytes
    - Viewed (0)
  4. 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)
  5. 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)
  6. 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)
  7. 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)
  8. 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)
  9. 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)
  10. 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)
Back to top