fix(api): corregir pantalla en blanco por SpaController interceptando assets estáticos#15
Merged
Merged
Conversation
… assets estáticos
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
1 participant
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.
What
Corrige la pantalla en blanco causada por el
SpaControllerdel PR #14 interceptando los archivos JS/CSS del frontend.Why
El patrón
/{path:[^\.]*}/**delSpaControllercapturaba rutas como/static/js/bundle.abc123.jsporquestaticno tiene punto pero/**acepta cualquier sub-ruta, incluidas las que contienen extensiones de archivo. Spring devolvíaindex.htmldonde el browser esperaba JavaScript, rompiendo la carga completa del frontend. Adicionalmente, elJwtAuthFilterretornaba 401 en cualquier request con token expirado, incluyendo navegaciones SPA, lo que impedía que React cargara para redirigir al login.Changes
SpaController.java: reemplaza el patrón/{path:[^\.]*}/**por patrones de profundidad fija (0–3 niveles) con regex[^\.]*en cada segmento, cubriendo todas las rutas del React Router sin interceptar assets estáticosJwtAuthFilter.java: limita el rechazo 401 por token expirado/inválido únicamente a rutas/api/**; las navegaciones SPA pasan al frontend para que React maneje la redirección al login