- Sort Score
- Result 10 results
- Languages All
Results 161 - 170 of 917 for Send (0.02 sec)
-
cmd/config-current.go
Description: "send server logs to webhook endpoints", MultipleTargets: true, }, config.HelpKV{ Key: config.AuditWebhookSubSys, Description: "send audit logs to webhook endpoints", MultipleTargets: true, }, config.HelpKV{ Key: config.AuditKafkaSubSys, Description: "send audit logs to kafka endpoints", MultipleTargets: true,
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 28.5K bytes - Viewed (0) -
docs/features/caching.md
### Conditional Cache Hit When cache flags require checking the cache results are still valid an early cacheConditionalHit event is received followed by a cache hit or miss. Critically in the cache hit scenario the server won’t send the response body. The response will have non-null `cacheResponse` and `networkResponse`. The cacheResponse will be used as the top level response only if the response code is HTTP/1.1 304 Not Modified. - CallStart
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sun Feb 06 02:19:09 UTC 2022 - 3.1K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/exec/Crawler.java
import org.codelibs.fess.timer.SystemMonitorTarget; import org.codelibs.fess.util.ComponentUtil; import org.codelibs.fess.util.SystemUtil; import org.codelibs.fess.util.ThreadDumpUtil; import org.dbflute.mail.send.hook.SMailCallbackContext; import org.kohsuke.args4j.CmdLineException; import org.kohsuke.args4j.CmdLineParser; import org.kohsuke.args4j.Option; import org.lastaflute.core.mail.Postbox;
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Aug 07 03:06:29 UTC 2025 - 31K bytes - Viewed (0) -
docs/smb3-features/02-persistent-handles-design.md
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 31.6K bytes - Viewed (0) -
docs/bucket/versioning/README.md
``` <VersioningConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> </VersioningConfiguration> ``` To enable versioning, you send a request to MinIO with a versioning configuration with Status set to `Enabled`. ``` <VersioningConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Status>Enabled</Status> </VersioningConfiguration> ```
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 12K bytes - Viewed (0) -
mockwebserver/src/test/java/mockwebserver3/internal/http2/Http2Server.kt
if (requestHeaders.name(i) == Header.TARGET_PATH_UTF8) { path = requestHeaders.value(i) break } i++ } if (path == null) { // TODO: send bad request error throw AssertionError() } val file = File(baseDirectory.toString() + path) if (file.isDirectory) { serveDirectory(stream, file.listFiles()!!)
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Thu Jul 31 04:18:40 UTC 2025 - 6.4K bytes - Viewed (0) -
src/main/java/jcifs/dcerpc/DcerpcPipeHandle.java
if (this.handle.isStale()) { throw new IOException("DCERPC pipe is no longer open"); } this.handle.send(buf, off, length); } @Override protected int doReceiveFragment(final byte[] buf) throws IOException { if (buf.length < getMaxRecv()) {
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 5.6K bytes - Viewed (0) -
docs/metrics/v3.md
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 45.2K bytes - Viewed (0) -
docs/en/docs/tutorial/background-tasks.md
This includes, for example: * Email notifications sent after performing an action: * As connecting to an email server and sending an email tends to be "slow" (several seconds), you can return the response right away and send the email notification in the background. * Processing data: * For example, let's say you receive a file that must go through a slow process, you can return a response of "Accepted" (HTTP 202) and process the file in the background.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 4.8K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
The application would process the request and send a **plain (unencrypted) HTTP response** to the TLS Termination Proxy. <img src="/img/deployment/https/https06.drawio.svg"> ### HTTPS Response { #https-response } The TLS Termination Proxy would then **encrypt the response** using the cryptography agreed before (that started with the certificate for `someapp.example.com`), and send it back to the browser.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 19:34:08 UTC 2025 - 14.3K bytes - Viewed (0)