release: {{ .Release.Name }} heritage: {{ .Release.Service }} spec: endpointSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - toPorts: - ports: - port: {{ .Values.minioAPIPort }} protocol: TCP - port: {{ .Values.minioConsolePort }} protocol: TCP {{- if not .Values.networkPolicy.allowExternal }} fromEndpoints: - matchLabels: {{ template "minio.name" . }}-client: "true" {{- end }} egress: {{- range $entity := .Values.networkPolicy.egressEntities }} - toEntities:...

{{ .Release.Name }} heritage: {{ .Release.Service }} spec: endpointSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - toPorts: - ports: - port: "{{ .Values.minioAPIPort }}" protocol: TCP - port: "{{ .Values.minioConsolePort }}" protocol: TCP {{- if not .Values.networkPolicy.allowExternal }} fromEndpoints: - matchLabels: {{ template "minio.name" . }}-client: "true" {{- end }} egress: {{- range $entity := .Values.networkPolicy.egressEntities }} - toEntities:...

kubernetes.io/ingress.class: nginx # kubernetes.io/tls-acme: "true" # kubernetes.io/ingress.allow-http: "false" # kubernetes.io/ingress.global-static-ip-name: "" # nginx.ingress.kubernetes.io/secure-backends: "true" # nginx.ingress.kubernetes.io/backend-protocol: "HTTPS" # nginx.ingress.kubernetes.io/whitelist-source-range: 0.0.0.0/0 path: / hosts: - minio-example.local tls: [] # - secretName: chart-example-tls # hosts: # - chart-example.local consoleService: type: ClusterIP clusterIP: ~ ## Make sure to...

 * License along with this library; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs;

/**
 * Utility class holding several protocol constrants
 *
 * @author mbechler
 *
 *
 * <p>This interface is intended for internal use.</p>
 */
public interface SmbConstants {

    /**
     * Default SMB port number for direct TCP transport.

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */

package jcifs.smb1.smb1;

/**
 * Interface defining NT status codes used in SMB1 protocol operations.
 * These status codes are returned by SMB servers to indicate the result
 * of requested operations. The codes follow the Windows NT status code format.
 */
public interface NtStatus {

//  	Content-Type + "\n" +
//  	Date + "\n" +
//  	CanonicalizedProtocolHeaders +
//  	CanonicalizedResource;
//
// CanonicalizedResource = [ SlashSeparator + Bucket ] +
//  	<HTTP-Request-URI, from the protocol name up to the query string> +
//  	[ subresource, if present. For example "?acl", "?location", "?logging", or "?torrent"];
//
// CanonicalizedProtocolHeaders = <described below>

 * </ul>
 *
 * <p>References:</p>
 * <ul>
 * <li><a href="https://datatracker.ietf.org/doc/html/rfc9309">RFC 9309 - Robots Exclusion Protocol</a></li>
 * <li><a href="https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt">
 * Google's robots.txt Specification</a></li>
 * </ul>
 *
 * @author bowez
 * @author shinsuke
 *
 */

        int cmd2 = (int) commandField.get(req2);

        assertEquals(cmd1, cmd2);
        assertEquals(SMB2_TREE_DISCONNECT, cmd1);
    }

    @Test
    @DisplayName("Should properly implement wire format protocol")
    void testWireFormatProtocol() {
        // Given
        Configuration mockConfig = mock(Configuration.class);
        Smb2TreeDisconnectRequest request = new Smb2TreeDisconnectRequest(mockConfig);

        response.prepare(mockRequest);

        // Then - method completes without error
        assertTrue(true);
    }

    @Test
    @DisplayName("Should verify wire format protocol compliance")
    void testWireFormatProtocolCompliance() throws SMBProtocolDecodingException {
        // Given - exact SMB2 TREE_DISCONNECT response structure

Une de :

* `POST`
* `GET`
* `PUT`
* `DELETE`

...ou une des plus exotiques :

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

Dans le protocol HTTP, vous pouvez communiquer avec chaque chemin en utilisant une (ou plus) de ces "méthodes".

---

En construisant des APIs, vous utilisez généralement ces méthodes HTTP spécifiques pour effectuer une action précise.