- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 28 for 443 (0.01 sec)
-
src/test/java/jcifs/smb1/https/HandlerTest.java
assertEquals(port2, port3); assertEquals(443, port1); } } @Nested @DisplayName("Constants Tests") class ConstantsTests { @Test @DisplayName("DEFAULT_HTTPS_PORT should be 443") void testDefaultHttpsPortValue() { // Then assertEquals(443, Handler.DEFAULT_HTTPS_PORT); } @Test
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Thu Aug 14 05:31:44 UTC 2025 - 6.2K bytes - Viewed (0) -
src/test/java/jcifs/https/HandlerTest.java
assertEquals(port2, port3); assertEquals(443, port1); } } @Nested @DisplayName("Constants Tests") class ConstantsTests { @Test @DisplayName("DEFAULT_HTTPS_PORT should be 443") void testDefaultHttpsPortValue() { // Then assertEquals(443, Handler.DEFAULT_HTTPS_PORT); } @Test
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Thu Aug 14 05:31:44 UTC 2025 - 6.6K bytes - Viewed (0) -
src/main/java/jcifs/https/Handler.java
* * @deprecated {@link NtlmHttpURLConnection} is broken by design. */ @Deprecated public class Handler extends jcifs.http.Handler { /** * The default HTTPS port (<code>443</code>). */ public static final int DEFAULT_HTTPS_PORT = 443; /** * Constructs an HTTPS handler with the specified CIFS context. * * @param tc context to use */ public Handler(final CIFSContext tc) {Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 1.9K bytes - Viewed (0) -
src/main/java/jcifs/smb1/https/Handler.java
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 1.6K bytes - Viewed (0) -
cmd/server-startup-msg.go
h, _, err := net.SplitHostPort(host) if err != nil { h = host } ip := net.ParseIP(h) return ip.To16() != nil && ip.To4() == nil } // strip api endpoints list with standard ports such as // port "80" and "443" before displaying on the startup // banner. Returns a new list of API endpoints. func stripStandardPorts(apiEndpoints []string, host string) (newAPIEndpoints []string) { if len(apiEndpoints) == 1 { return apiEndpoints }
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 6.2K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/Route.kt
return result } /** * Returns a string with the URL hostname, socket IP address, and socket port, like one of these: * * * `example.com:80 at 1.2.3.4:8888` * * `example.com:443 via proxy [::1]:8888` * * This omits duplicate information when possible. */ override fun toString(): String = buildString { val addressHostname = address.url.host // Already in canonical form.
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 4.2K bytes - Viewed (0) -
mockwebserver/src/main/kotlin/mockwebserver3/RecordedRequest.kt
* header to create the request URL. * * For HTTP proxy requests this will be either an absolute-form string like * `http://example.com/index.html` (HTTP proxy) or an authority-form string like * `example.com:443` (HTTPS proxy). * * For OPTIONS requests, this may be an asterisk, `*`. */ public val target: String, /** A string like `HTTP/1.1` or `HTTP/2`. */ public val version: String,
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Sat Jun 21 20:36:35 UTC 2025 - 3.2K bytes - Viewed (1) -
docs/en/docs/deployment/https.md
<img src="/img/deployment/https/https01.drawio.svg"> ### TLS Handshake Start { #tls-handshake-start } The browser would then communicate with that IP address on **port 443** (the HTTPS port). The first part of the communication is just to establish the connection between the client and the server and to decide the cryptographic keys they will use, etc.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sun Aug 31 19:34:08 UTC 2025 - 14.3K bytes - Viewed (0) -
internal/handlers/forwarder.go
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Feb 18 16:25:55 UTC 2025 - 5.7K bytes - Viewed (0) -
docs/pt/docs/deployment/https.md
<img src="/img/deployment/https/https01.drawio.svg"> ### Início do Handshake TLS { #tls-handshake-start } O navegador então irá comunicar-se com esse endereço IP na porta 443 (a porta HTTPS). A primeira parte dessa comunicação é apenas para estabelecer a conexão entre o cliente e o servidor e para decidir as chaves criptográficas a serem utilizadas, etc.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Nov 12 16:23:57 UTC 2025 - 14.8K bytes - Viewed (0)