Absolutely—you can modify your URL to point to a custom port and rewrite the HTTPS URL from https://subdomain.example.tech:8081/ to https://subdomain.example.tech/something/ in a Docker environment. The core solution here is using a reverse proxy to handle URL rewriting and port mapping. Below are two practical, widely adopted approaches:

Option 1: Use Nginx (Manual, Fine-Grained Control) #

Nginx is a classic reverse proxy that gives you full control over routing rules. Here's how to set it up:

Step 1: Create an Nginx Configuration File #

Make a file named proxy.conf with the following content to define routing and SSL settings:

server {
    listen 443 ssl;
    server_name subdomain.example.tech;

    # Replace with your actual SSL certificate paths
    ssl_certificate /certs/fullchain.pem;
    ssl_certificate_key /certs/privkey.pem;

    # Route requests to /something/ to your backend container's 8081 port
    location /something/ {
        proxy_pass https://your-backend-container:8081/;
        # Critical headers to ensure your backend service behaves correctly
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

• Swap your-backend-container with the name of your target Docker container.
• Ensure your SSL certificates (e.g., from Let’s Encrypt) are stored in a directory you can mount into the Nginx container.

Step 2: Run the Nginx Container #

Launch the Nginx container with your config and certificates mounted, and connect it to the same Docker network as your backend service:

docker run -d \
  --name nginx-proxy \
  -p 443:443 \
  -v $(pwd)/proxy.conf:/etc/nginx/conf.d/default.conf \
  -v /path/to/your/ssl/certs:/certs \
  --network your-shared-docker-network \
  nginx:alpine

• Make sure your backend container is also attached to your-shared-docker-network so Nginx can reach it.

Option 2: Use Traefik (Automated, Docker-Native) #

Traefik is built for containerized environments and automates routing, SSL certificate management, and more. It’s perfect if you want to avoid manual config files.

Step 1: Set Up a Docker Compose File #

Create a docker-compose.yml file that includes Traefik and your backend service:

version: '3.8'

services:
  traefik:
    image: traefik:v2.10
    command:
      - "--api.insecure=false" # Disable in production; secure the dashboard if needed
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.websecure.address=:443"
      # Configure Let's Encrypt for automatic SSL certificates
      - "--certificatesresolvers.le.acme.httpchallenge=true"
      - "--certificatesresolvers.le.acme.httpchallenge.entrypoint=web"
      - "--certificatesresolvers.le.acme.email=your-email@example.com"
      - "--certificatesresolvers.le.acme.storage=/letsencrypt/acme.json"
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock:ro" # Let Traefik read Docker metadata
      - "./letsencrypt:/letsencrypt" # Store SSL certificates

  your-backend-service:
    image: your-backend-image:latest
    labels:
      - "traefik.enable=true"
      # Define routing rule: match subdomain and /something/ path
      - "traefik.http.routers.backend.rule=Host(`subdomain.example.tech`) && PathPrefix(`/something/`)"
      - "traefik.http.routers.backend.entrypoints=websecure"
      - "traefik.http.routers.backend.tls.certresolver=le"
      # Strip /something/ prefix before forwarding to backend
      - "traefik.http.middlewares.strip-prefix.stripprefix.prefixes=/something"
      - "traefik.http.routers.backend.middlewares=strip-prefix@docker"
      # Point to your backend's custom port (8081)
      - "traefik.http.services.backend.loadbalancer.server.port=8081"

Step 2: Launch the Services #

Run the stack with:

docker-compose up -d

Traefik will automatically generate SSL certificates for your subdomain, route requests to /something/ to your backend’s 8081 port, and strip the path prefix so your backend receives clean requests.

Key Notes #

• Docker Networks: Both solutions require your reverse proxy and backend service to be on the same Docker network (default or custom) so they can communicate via container names.
• SSL Certificates: For HTTPS, valid certificates are required—both Nginx and Traefik work seamlessly with Let’s Encrypt for free, automated certificates.
• Path Prefix: If your backend expects requests under /something/ instead of the root, remove the stripprefix middleware in Traefik or adjust the proxy_pass path in Nginx.

内容的提问来源于stack exchange，提问作者Masteredgod