But there are specific cases where it's useful to get the `Request` object.

## Use the `Request` object directly { #use-the-request-object-directly }

Let's imagine you want to get the client's IP address/host inside of your *path operation function*.

For that you need to access the request directly.

{* ../../docs_src/using_request_directly/tutorial001.py hl[1,7:8] *}

        SMBUtil.writeInt2(stringDataStart - 8, buffer, 20); // Offset from start of referral

        // DFS alternate path offset (2 bytes)
        SMBUtil.writeInt2(0, buffer, 22);

        // Network address offset (2 bytes)
        SMBUtil.writeInt2(0, buffer, 24);

        // Padding to align string data
        buffer[26] = 0;
        buffer[27] = 0;

        // Add the path string at stringDataStart

                addresses = new UniAddress[1];
                addresses[0] = UniAddress.getByName(server);
                return getNextAddress();
            }
            final String address = queryLookup(query, "address");
            if (address != null && address.length() > 0) {
                final byte[] ip = java.net.InetAddress.getByName(address).getAddress();

      .Builder()
      .heldCertificate(heldCertificate)
      .addTrustedCertificate(heldCertificate.certificate)
      .build()
  }

  /** Returns an SSL client for this host's localhost address. */
  @JvmStatic
  fun localhost(): HandshakeCertificates = localhost

  /** Returns a trust manager that trusts `trustedCertificates`. */
  @JvmStatic @IgnoreJRERequirement
  fun newTrustManager(

      required: true
  - type: markdown
    attributes:
      value: |
        Please make sure that this is a bug. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub.

  - type: dropdown
    id: tf-nightly
    attributes:
      label: Have you reproduced the bug with TensorFlow Nightly?

			purge "${MC_BUILD_DIR}"
			exit 1
		fi

		(cd "${MC_BUILD_DIR}" && go build -o "$C_PWD/mc")

		# remove mc source.
		purge "${MC_BUILD_DIR}"
	fi

	"${MINIO[@]}" --address ":$start_port" "${WORK_DIR}/disk{1...10}" >"${WORK_DIR}/server1.log" 2>&1 &
	pid=$!
	disown $pid
	sleep 5

	if ! ps -p ${pid} 1>&2 >/dev/null; then
		echo "server1 log:"
		cat "${WORK_DIR}/server1.log"

use your browser or the Minio SDK to access the server - https://docs.minio.io/categories/17 {{- end }} {{- if eq .Values.service.type "LoadBalancer" }} Minio can be accessed via port {{ .Values.service.port }} on an external IP address. Get the service external IP address by: kubectl get svc --namespace {{ .Release.Namespace }} -l app={{ template "minio.fullname" . }} Note that the public IP may take a couple of minutes to be available. You can now access Minio server on http://<External-IP>:9000....

    private SocketChannel socketChannel;
    private Socket socket;

    /**
     * Create new TCP RDMA connection
     *
     * @param remote remote socket address
     * @param local local socket address, may be null
     */
    public TcpRdmaConnection(InetSocketAddress remote, InetSocketAddress local) {
        super(remote, local);
    }

    @Override

import jakarta.servlet.http.HttpServlet;
import jakarta.servlet.http.HttpServletRequest;
import jakarta.servlet.http.HttpServletResponse;
import jakarta.servlet.http.HttpSession;
import jcifs.Address;
import jcifs.CIFSContext;
import jcifs.CIFSException;
import jcifs.Config;
import jcifs.config.PropertyConfiguration;
import jcifs.context.BaseContext;
import jcifs.netbios.UniAddress;

* 3.1 [Use certgen to Generate a Certificate](#using-go)
* 3.2 [Use OpenSSL to Generate a Certificate](#using-open-ssl)
* 3.3 [Use OpenSSL (with IP address) to Generate a Certificate](#using-open-ssl-with-ip)
* 3.4 [Use GnuTLS (for Windows) to Generate a Certificate](#using-gnu-tls)

**Note:**

* MinIO only supports keys and certificates in PEM format on Linux and Windows.