Search Options

Results per page
Sort
Preferred Languages
Advance

Results 21 - 30 of 448 for seni (0.02 sec)

  1. src/main/java/org/codelibs/curl/Curl.java

         */
        protected Curl() {
            // nothing
        }
    
        /**
         * Creates a new CurlRequest with the HTTP GET method for the specified URL.
         *
         * @param url the URL to send the GET request to
         * @return a CurlRequest object configured with the GET method and the specified URL
         */
        public static CurlRequest get(final String url) {
            return new CurlRequest(Method.GET, url);
        }
    Registered: Thu Sep 04 15:34:10 UTC 2025
    - Last Modified: Sat Jul 05 01:38:18 UTC 2025
    - 5.5K bytes
    - Viewed (0)
  2. 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 Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 2.7K bytes
    - Viewed (0)
  3. src/main/java/jcifs/internal/smb2/multichannel/ChannelManager.java

            // Note: This IOCTL must be sent on an existing session
            // The actual sending would need integration with the session's transport
            // For now, we're preparing the request structure correctly
    
            // TODO: Integration point - send request through session.send()
            // Smb2IoctlResponse response = (Smb2IoctlResponse) session.send(request);
            // if (response.isSuccess()) {
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Thu Aug 21 11:13:46 UTC 2025
    - 20K bytes
    - Viewed (0)
  4. okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/ConnectPlan.kt

            // Assume the server won't send a TLS ServerHello until we send a TLS ClientHello. If
            // that happens, then we will have buffered bytes that are needed by the SSLSocket!
            // This check is imperfect: it doesn't tell us whether a handshake will succeed, just
            // that it will almost certainly fail because the proxy has sent unexpected data.
    Registered: Fri Sep 05 11:42:10 UTC 2025
    - Last Modified: Thu Jul 31 04:18:40 UTC 2025
    - 18.6K bytes
    - Viewed (0)
  5. src/main/java/jcifs/internal/smb2/rdma/SmbDirectNegotiateResponse.java

        }
    
        /**
         * Get the preferred size for send operations
         *
         * @return preferred send size in bytes
         */
        public int getPreferredSendSize() {
            return preferredSendSize;
        }
    
        /**
         * Set the preferred size for send operations
         *
         * @param preferredSendSize preferred send size in bytes
         */
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Sun Aug 24 00:12:28 UTC 2025
    - 9.3K bytes
    - Viewed (0)
  6. docs/em/docs/tutorial/dependencies/dependencies-with-yield.md

            dep -->> handler: Auto forward exception
        end
        operation ->> client: Return response to client
        Note over client,operation: Response is already sent, can't change it anymore
        opt Tasks
            operation -->> tasks: Send background tasks
        end
        opt Raise other exception
            tasks -->> dep: Raise other exception
        end
        Note over dep: After yield
        opt Handle other exception
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Mon Nov 18 02:25:44 UTC 2024
    - 8.4K bytes
    - Viewed (0)
  7. docs/en/docs/advanced/openapi-callbacks.md

    The user of your API (an external developer) will create an invoice in your API with a POST request.
    
    Then your API will (let's imagine):
    
    * Send the invoice to some customer of the external developer.
    * Collect the money.
    * Send a notification back to the API user (the external developer).
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 7.9K bytes
    - Viewed (0)
  8. 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)
  9. src/main/java/jcifs/netbios/NameServiceClientImpl.java

            }
    
            do {
                try {
                    send(request, response, config.getNetbiosRetryTimeout());
                } catch (final InterruptedIOException ioe) {
                    // second query thread to finish gets interrupted so this is expected
                    if (log.isTraceEnabled()) {
                        log.trace("Failed to send nameservice request for " + name.name, ioe);
                    }
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Sat Aug 30 05:58:03 UTC 2025
    - 38.5K bytes
    - Viewed (0)
  10. 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:
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 4.8K bytes
    - Viewed (0)
Back to top