Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Allow an HTTP base_url for model providers, like OAC_PUBLIC_URL already does

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

Los mantenedores suelen responder en 1 día

@velrith ya está trabajando en esto.

Desde el 4/10/2026.

  • #417 de @velrith — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
go
Área
backend-api-design

Línea de trabajo

Read contracts/agents-api/v1/model_provider_admission.go, especially providerScheme and validModelProviderBaseURL, and compare the private-host HTTP rules in internal/origin and deployment/public_url.go. Check the tests covering model provider base URL validation. Done means HTTP is accepted only for loopback or literal private ranges, HTTPS remains required elsewhere, and the linked pull request's behavior is covered by tests.

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

Descripción

What I'm asking for

Let a deployment default model provider be configured with an http:// base_url, instead of requiring https://.

Where it's blocked

contracts/agents-api/v1/model_provider_admission.go:12 hard-codes providerScheme = "https", and validModelProviderBaseURL rejects anything else. So PUT /core/v1/harnesses/{harness}/model-configuration returns 400 model_provider_base_url_invalid for a perfectly reachable local endpoint, e.g. http://127.0.0.1:7351 or http://10.0.0.5:8080.

This is a distinct surface from #398 / #408: those changed the public URL and the node paths. The model provider base_url keeps the unconditional HTTPS rule.

Why this looks inconsistent

The repo already treats plain HTTP as acceptable where it does not leave the trust boundary:

  • #408 made OAC_PUBLIC_URL accept http on loopback and literal private ranges (internal/origin, deployment/public_url.go).
  • The model path's own credential gateway serves the Harness over loopback in plaintext by design (#343): the Harness never holds the key, so the relay is a local HTTP service.

The provider base_url is the one remaining surface that maps http to "invalid" unconditionally, even when the host is the same loopback the gateway already uses.

Concrete case, not hypothetical

I run a self-hosted model proxy on this host (an OpenAI / Anthropic / Responses-compatible gateway on 127.0.0.1:7351) and I want the Harnesses to use it. Today the only way through is to stand up a TLS terminator in front of it and install a self-signed CA into the Runtime image's trust store — extra moving parts for a connection that never leaves the machine.

Suggested shape

Accept http where the same rule the rest of Core already uses says it is safe — loopback, or literal private ranges — and keep https required everywhere else. That mirrors #408 exactly and keeps the current default unchanged. If you would rather make it explicit, an opt-in works too.

I am not asking to drop TLS. A plain-HTTP exception limited to loopback/private hosts would cover the local-proxy case without weakening anything reachable from the network.

Lenguaje dominante
Go
Estrellas
182
Forks
17
Merge medio
1 h 15 min
PR fusionados (30 d)
360

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 MiniMax-AI/OpenAgentCore

Todos los issues de MiniMax-AI/OpenAgentCore

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.