- Sort Score
- Result 10 results
- Languages All
Results 121 - 130 of 267 for clientes (0.04 sec)
-
samples/compare/src/test/kotlin/okhttp3/compare/JavaHttpClientTest.kt
import okhttp3.testing.PlatformVersion import org.junit.jupiter.api.Test import org.junit.jupiter.api.extension.RegisterExtension /** * Java HTTP Client. * * https://openjdk.java.net/groups/net/httpclient/intro.html * * Baseline test if we ned to validate OkHttp behaviour against other popular clients. */ class JavaHttpClientTest { @JvmField @RegisterExtension val platform = PlatformRule() @StartStopRegistered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Wed Jun 18 12:28:21 UTC 2025 - 2.8K bytes - Viewed (0) -
docs/es/docs/advanced/response-directly.md
Luego, detrás de escena, pondría esos datos compatibles con JSON (por ejemplo, un `dict`) dentro de un `JSONResponse` que se usaría para enviar el response al cliente. Pero puedes devolver un `JSONResponse` directamente desde tus *path operations*. Esto podría ser útil, por ejemplo, para devolver headers o cookies personalizados. ## Devolver una `Response` { #return-a-response }
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 3.4K bytes - Viewed (0) -
docs/pt/docs/advanced/response-directly.md
Então, por baixo dos panos, ele incluiria esses dados compatíveis com JSON (e.g. um `dict`) dentro de uma `JSONResponse` que é utilizada para enviar uma resposta para o cliente. Mas você pode retornar a `JSONResponse` diretamente nas suas *operações de rota*. Pode ser útil para retornar cabeçalhos e cookies personalizados, por exemplo. ## Retornando uma `Response` { #return-a-response }
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 3.5K bytes - Viewed (0) -
docs/de/docs/how-to/separate-openapi-schemas.md
Der Hauptanwendungsfall hierfür besteht wahrscheinlich darin, dass Sie das mal tun möchten, wenn Sie bereits über einige automatisch generierte Client-Codes/SDKs verfügen und im Moment nicht alle automatisch generierten Client-Codes/SDKs aktualisieren möchten, möglicherweise später, aber nicht jetzt. In diesem Fall können Sie diese Funktion in **FastAPI** mit dem Parameter `separate_input_output_schemas=False` deaktivieren.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 24 10:28:19 UTC 2025 - 5.2K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/util/SearchEngineUtil.java
* @return the number of documents processed */ public static long scroll(final String index, final Function<SearchHit, Boolean> callback) { final SearchEngineClient client = ComponentUtil.getSearchEngineClient(); return client.<SearchHit> scrollSearch(index, searchRequestBuilder -> true, (searchResponse, hit) -> hit, hit -> callback.apply(hit)); } /**Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 5.1K bytes - Viewed (0) -
src/main/java/jcifs/http/NtlmSsp.java
* hashes via NTLM SSP with MSIE. It might also be used directly by servlet * containers to incorporate similar functionality. * <p> * How NTLMSSP is used in conjunction with HTTP and MSIE clients is * described in an <A HREF="http://www.innovation.ch/java/ntlm.html">NTLM * Authentication Scheme for HTTP</A>. * <p> * Also, read <a * href="../../../ntlmhttpauth.html">jCIFS NTLM HTTP Authentication and
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 4.9K bytes - Viewed (0) -
docs/de/docs/advanced/using-request-directly.md
Es gibt jedoch bestimmte Fälle, in denen es nützlich ist, auf das `Request`-Objekt zuzugreifen. ## Das `Request`-Objekt direkt verwenden { #use-the-request-object-directly } Angenommen, Sie möchten auf die IP-Adresse/den Host des Clients in Ihrer *Pfadoperation-Funktion* zugreifen. Dazu müssen Sie direkt auf den Request zugreifen. {* ../../docs_src/using_request_directly/tutorial001_py39.py hl[1,7:8] *}Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 2.7K bytes - Viewed (0) -
src/main/java/jcifs/smb1/http/NtlmHttpFilter.java
/** * Negotiate password hashes with MSIE clients using NTLM SSP * @param req The servlet request * @param resp The servlet response * @param skipAuthentication If true the negotiation is only done if it is * initiated by the client (MSIE post requests after successful NTLM SSP * authentication). If false and the user has not been authenticated yet * the client will be forced to send an authentication (server sendsRegistered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 30 05:58:03 UTC 2025 - 11.3K bytes - Viewed (0) -
docs/features/calls.md
# Calls The HTTP client’s job is to accept your request and produce its response. This is simple in theory but it gets tricky in practice. ## [Requests](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-request/) Each HTTP request contains a URL, a method (like `GET` or `POST`), and a list of headers. Requests may also contain a body: a data stream of a specific content type. ## [Responses](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-response/)
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Sun Feb 06 02:19:09 UTC 2022 - 3.9K bytes - Viewed (0) -
docs/pt/docs/advanced/using-request-directly.md
Mas há situações específicas onde é útil utilizar o objeto `Request`. ## Utilize o objeto `Request` diretamente { #use-the-request-object-directly } Vamos imaginar que você deseja obter o endereço de IP/host do cliente dentro da sua *função de operação de rota*. Para isso você precisa acessar a requisição diretamente. {* ../../docs_src/using_request_directly/tutorial001_py39.py hl[1,7:8] *}Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 2.7K bytes - Viewed (0)