fix: resolve mixed content on login and static asset routing#23
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Descrição
Este Pull Request resolve o bloqueio crítico do formulário de login em produção e corrige o carregamento de arquivos estáticos, como
logo.svg, garantindo o funcionamento correto da aplicação no domínio principal.As alterações também melhoram a integração entre frontend, NGINX e backend dentro do ambiente Kubernetes.
Problemas Resolvidos
Mixed Content & CORS — Login em Produção
config.jsmantinha uma referência hardcoded para:http://localhost:8080HTTPSeHTTP(Mixed Content);localhostinexistente no contexto do client;Solução Aplicada
API_URLfoi ajustada para utilizar rotas relativas:Resultado
Correção de Routing de Assets no NGINX
Problema
logo.svg, retornavam404em alguns cenários devido a resoluções internas incorretas do NGINX.✅ Solução Aplicada
try_filesno bloco de cache de assets do
nginx.conf.Resultado
404causados por fallback incorreto de rotas.Integração com GitOps / ArgoCD
Impactos Esperados