- Sort Score
- Result 10 results
- Languages All
Results 331 - 340 of 1,584 for Requests (0.04 sec)
-
README.md
We welcome pull requests for your language. ### Translations - [日本語 (Japanese)](docs/ja/README.md) - [简体中文 (Simplified Chinese)](docs/zh-CN/README.md) - [Español (Spanish)](docs/es/README.md)
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Jul 10 06:34:32 UTC 2025 - 7.2K bytes - Viewed (2) -
android/guava/src/com/google/common/util/concurrent/ThreadFactoryBuilder.java
// At least, I assume that's why. TODO(cpovirk): Check, and maybe add a test for this. @SuppressWarnings("ThreadPriorityCheck") // We only propagate user requests (which we discourage). private static ThreadFactory doBuild(ThreadFactoryBuilder builder) { String nameFormat = builder.nameFormat; Boolean daemon = builder.daemon; Integer priority = builder.priority;
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Sat Aug 09 01:35:26 UTC 2025 - 9K bytes - Viewed (0) -
fess-crawler/src/main/java/org/codelibs/fess/crawler/entity/RobotsTxt.java
return directive.allows(path); } /** * Gets the crawl delay value for the specified user agent from robots.txt. * The crawl delay specifies the time (in seconds) to wait between successive requests. * * @param userAgent The user agent string to match against robots.txt directives * @return The crawl delay value in seconds. Returns 0 if no matching directive is found
Registered: Sun Sep 21 03:50:09 UTC 2025 - Last Modified: Sun Jul 06 02:13:03 UTC 2025 - 10K bytes - Viewed (0) -
src/main/java/jcifs/internal/fscc/SmbInfoAllocation.java
import jcifs.internal.AllocInfo; import jcifs.internal.SMBProtocolDecodingException; import jcifs.internal.util.SMBUtil; /** * Represents the SMB_INFO_ALLOCATION information level used in SMB transaction requests. * This structure provides allocation information for a file system including total units, * free units, sectors per allocation unit, and bytes per sector. */ public class SmbInfoAllocation implements AllocInfo {
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 2.9K bytes - Viewed (0) -
ci/official/utilities/setup_docker.sh
-v "$TFCI_GIT_DIR:$WORKING_DIR" \ --env-file "$env_file" \ "$TFCI_DOCKER_IMAGE" \ bash if [[ "$is_windows" == true ]]; then # Allow requests from the container. # Additional setup is contained in ci/official/envs/rbe. CONTAINER_IP_ADDR=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' tf)
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Thu Jan 09 18:37:25 UTC 2025 - 2.6K bytes - Viewed (0) -
docs/en/docs/deployment/server-workers.md
When deploying applications you will probably want to have some **replication of processes** to take advantage of **multiple cores** and to be able to handle more requests. As you saw in the previous chapter about [Deployment Concepts](concepts.md){.internal-link target=_blank}, there are multiple strategies you can use.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 8.3K bytes - Viewed (0) -
src/main/java/jcifs/smb1/smb1/ServerMessageBlock.java
} /* * These are all the smbs supported by this library. This includes requests * and well as their responses for each type however the actuall implementations * of the readXxxWireFormat and writeXxxWireFormat methods may not be in * place. For example at the time of this writing the readXxxWireFormat * for requests and the writeXxxWireFormat for responses are not implemented
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Thu Aug 14 07:14:38 UTC 2025 - 19.7K bytes - Viewed (0) -
mockwebserver-deprecated/src/main/kotlin/okhttp3/mockwebserver/RecordedRequest.kt
// 2001:db8:85a3::8a2e:370:7334 // ::1 hostname = "[$hostname]" } val localPort = socket.localPort // Allow null in failure case to allow for testing bad requests this.requestUrl = "$scheme://$hostname:$localPort$path".toHttpUrlOrNull() } else { this.requestUrl = null this.method = null this.path = null } } @Deprecated(
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Mon Jan 08 01:13:22 UTC 2024 - 4.1K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/entity/GeoInfo.java
* geo-distance queries for each configured geographic field. * * @param request the HTTP servlet request containing geographic parameters * @throws InvalidQueryException if geo point format is invalid or parsing fails */ public GeoInfo(final HttpServletRequest request) { final FessConfig fessConfig = ComponentUtil.getFessConfig();
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 5.7K bytes - Viewed (0) -
docs/de/docs/advanced/generate-clients.md
Beachten Sie, dass die *Pfadoperationen* die Modelle definieren, welche diese für die Request- und Response-<abbr title="Die eigentlichen Nutzdaten, abzüglich der Metadaten">Payload</abbr> verwenden, indem sie die Modelle `Item` und `ResponseMessage` verwenden. ### API-Dokumentation Wenn Sie zur API-Dokumentation gehen, werden Sie sehen, dass diese die **Schemas** für die Daten enthält, welche in Requests gesendet und in Responses empfangen werden:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Tue Jun 17 11:53:56 UTC 2025 - 11.4K bytes - Viewed (0)