Search Options

Results per page
Sort
Preferred Languages
Advance

Results 251 - 260 of 446 for ssec (0.08 sec)

  1. cmd/s3-zip-handlers.go

    	if crypto.S3.IsRequested(r.Header) || crypto.S3KMS.IsRequested(r.Header) { // If SSE-S3 or SSE-KMS present -> AWS fails with undefined error
    		writeErrorResponse(ctx, w, errorCodes.ToAPIErr(ErrBadRequest), r.URL)
    		return
    	}
    
    	zipPath, object, err := splitZipExtensionPath(object)
    	if err != nil {
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Aug 29 02:39:48 UTC 2025
    - 15.8K bytes
    - Viewed (0)
  2. docs/debugging/s3-check-md5/main.go

    				log.Println("SKIPPED: Objects encrypted with SSE-C do not have md5sum as ETag:", objFullPath(object))
    				continue
    			}
    			if v, ok := object.UserMetadata["X-Amz-Server-Side-Encryption"]; ok && v == "aws:kms" {
    				log.Println("SKIPPED: encrypted with SSE-KMS do not have md5sum as ETag:", objFullPath(object))
    				continue
    			}
    			parts := 1
    			multipart := false
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Sep 28 20:59:21 UTC 2025
    - 6.3K bytes
    - Viewed (0)
  3. docs/es/docs/tutorial/request-forms.md

    Por ejemplo, en una de las formas en las que se puede usar la especificación OAuth2 (llamada "password flow") se requiere enviar un `username` y `password` como campos de formulario.
    
    La <abbr title="specification – especificación">spec</abbr> requiere que los campos se llamen exactamente `username` y `password`, y que se envíen como campos de formulario, no JSON.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Tue Dec 16 16:33:45 UTC 2025
    - 3.1K bytes
    - Viewed (0)
  4. docs/en/docs/tutorial/request-forms.md

    For example, in one of the ways the OAuth2 specification can be used (called "password flow") it is required to send a `username` and `password` as form fields.
    
    The <abbr title="specification">spec</abbr> requires the fields to be exactly named `username` and `password`, and to be sent as form fields, not JSON.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 2.7K bytes
    - Viewed (0)
  5. guava/src/com/google/common/cache/CacheBuilder.java

       *
       * @since 12.0
       */
      @GwtIncompatible // To be supported
      public static CacheBuilder<Object, Object> from(CacheBuilderSpec spec) {
        return spec.toCacheBuilder().lenientParsing();
      }
    
      /**
       * Constructs a new {@code CacheBuilder} instance with the settings specified in {@code spec}.
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Wed Oct 08 18:55:33 UTC 2025
    - 51.6K bytes
    - Viewed (0)
  6. docs/pt/docs/tutorial/request-forms.md

    Por exemplo, em uma das maneiras que a especificação OAuth2 pode ser usada (chamada "fluxo de senha"), é necessário enviar um `username` e uma `password` como campos do formulário.
    
    A <abbr title="specification – especificação">spec</abbr> exige que os campos sejam exatamente nomeados como `username` e `password` e sejam enviados como campos de formulário, não JSON.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Nov 12 16:23:57 UTC 2025
    - 3.1K bytes
    - Viewed (0)
  7. src/main/webapp/WEB-INF/orig/view/profile/index.jsp

    <%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%><!DOCTYPE html>
    ${fe:html(true)}
    <head profile="http://a9.com/-/spec/opensearch/1.1/">
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <title><la:message key="labels.profile.title" /></title>
    <link href="${fe:url('/css/admin/bootstrap.min.css')}" rel="stylesheet" type="text/css" />
    Registered: Sat Dec 20 09:19:18 UTC 2025
    - Last Modified: Sat Jan 18 12:09:07 UTC 2025
    - 3.6K bytes
    - Viewed (0)
  8. docs/sts/dex.md

    ~ export MINIO_IDENTITY_OPENID_CONFIG_URL=http://127.0.0.1:5556/dex/.well-known/openid-configuration
    ~ minio server ~/test
    ```
    
    ### Run the `web-identity.go`
    
    ```
    ~ go run web-identity.go -cid example-app -csec ZXhhbXBsZS1hcHAtc2VjcmV0 \
         -config-ep http://127.0.0.1:5556/dex/.well-known/openid-configuration \
         -cscopes groups,openid,email,profile
    ```
    
    ```
    ~ mc admin policy create admin allaccess.json
    ```
    
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 3.8K bytes
    - Viewed (0)
  9. docs/bucket/versioning/DESIGN.md

    - ObjectType (default)
    - LegacyObjectType (preserves existing deployments and older xl.json format)
    - DeleteMarker (a versionId to capture the DELETE sequences implemented primarily for AWS spec compatibility)
    
    A sample msgpack-JSON `xl.meta`, you can debug the content inside `xl.meta` using [xl-meta.go](https://github.com/minio/minio/tree/master/docs/debugging#decoding-metadata) program.
    
    ```json
    {
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Jul 17 15:43:14 UTC 2022
    - 5.8K bytes
    - Viewed (0)
  10. guava-tests/test/com/google/common/primitives/IntsTest.java

      }
    
      // We need to test that our method behaves like the JDK method.
      @SuppressWarnings("InlineMeInliner")
      public void testCompare() {
        for (int x : VALUES) {
          for (int y : VALUES) {
            // note: spec requires only that the sign is the same
            assertWithMessage("%s, %s", x, y).that(Ints.compare(x, y)).isEqualTo(Integer.compare(x, y));
          }
        }
      }
    
      public void testContains() {
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Thu Dec 11 20:45:32 UTC 2025
    - 29.3K bytes
    - Viewed (0)
Back to top