- Sort Score
- Result 10 results
- Languages All
Results 131 - 140 of 998 for Included (0.04 sec)
-
LICENSES/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri May 08 04:49:00 UTC 2020 - 11.3K bytes - Viewed (0) -
LICENSES/vendor/github.com/NYTimes/gziphandler/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Feb 03 21:57:36 UTC 2021 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/container-storage-interface/spec/LICENSE
boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri May 08 04:49:00 UTC 2020 - 11.3K bytes - Viewed (0) -
LICENSES/vendor/github.com/coreos/go-semver/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri May 08 04:49:00 UTC 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/google/btree/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri May 08 04:49:00 UTC 2020 - 11.2K bytes - Viewed (0) -
LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Registered: Fri Sep 05 20:58:11 UTC 2025 - Last Modified: Fri Apr 18 13:54:00 UTC 2025 - 11.1K bytes - Viewed (0) -
apache-maven/src/main/appended-resources/licenses/Apache-2.0.txt
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Registered: Sun Sep 07 03:35:12 UTC 2025 - Last Modified: Tue Jan 28 11:47:17 UTC 2020 - 11.1K bytes - Viewed (0) -
samples/guide/src/main/java/okhttp3/recipes/CustomCipherSuites.java
public CustomCipherSuites() throws GeneralSecurityException { // Configure cipher suites to demonstrate how to customize which cipher suites will be used for // an OkHttp request. In order to be selected a cipher suite must be included in both OkHttp's // connection spec and in the SSLSocket's enabled cipher suites array. Most applications should // not customize the cipher suites list. List<CipherSuite> customCipherSuites = asList(
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Thu Mar 14 21:57:42 UTC 2019 - 6.5K bytes - Viewed (0) -
docs/sts/assume-role.md
"Expiration": "2019-02-20T19:56:59-08:00", "AccessKeyId": "K9DTIMUVZXEXJL3ATUOY" } } ``` ### Testing an example with `assume-role.go` The included program in this directory can also be used for testing: ``` shell $ go run assume-role.go -u foobar -p foo12345 -d Only displaying credentials: AccessKeyID: 27YDRYEM0S9B44AJJX9X
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 7.2K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/entity/FacetInfo.java
public String[] query; /** Maximum number of facet values to return */ public Integer size; /** Minimum document count required for a facet value to be included */ public Long minDocCount; /** Sort order for facet values (e.g., "count.desc", "term.asc") */ public String sort; /** Value to use for documents that don't have the facet field */
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 5.3K bytes - Viewed (0)