Redirect plain HTTP to HTTPS on direct TLS

Abierto
  • ¿Algo no está bien?
#440 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go
Área
backend

Línea de trabajo

Read internal/server/http.go and the TLS guide at site/src/content/docs/docs/guides/tls.mdx; first trace how direct TLS and FANOUT_PUBLIC_URL are configured. The issue is explicitly deferred until users request it, so confirm that demand exists before starting. Done means an opt-in port 80 listener redirects only to the configured HTTPS origin, startup rejects the setting without TLS, and the configuration reference and guide are updated.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

[!NOTE]
Deferred. Reverse proxies and CDNs already do this redirect, and a built-in one needs a second listener, which departs from the one-port design. Pick this up if people running direct TLS ask for it.

What

With direct TLS, the single listener serves only HTTPS, so someone who types a bare hostname into a browser gets a connection failure. An optional listener on port 80 could answer with a redirect to the HTTPS origin.

Acceptance criteria

  • Off by default; the one-port deployment is unchanged unless the setting is present
  • The listener serves only redirects, with no API, UI, MCP, or OTLP on it
  • The redirect target comes from configuration (FANOUT_PUBLIC_URL), never from the request Host header
  • Startup fails with an error naming the setting when TLS is not enabled
  • Configuration reference and TLS guide updated

References

  • internal/server/http.go
  • site/src/content/docs/docs/guides/tls.mdx

One pull request. Use the latest stable version of any dependency added, verified against its registry and pinned exactly.

Lenguaje dominante
Go
Estrellas
11
Forks
0
Merge medio
7 h 5 min
PR fusionados (30 d)
112

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de labstack/fanout

Todos los issues de labstack/fanout

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.