Skip to content

Conversation

@gigi206
Copy link

@gigi206 gigi206 commented Dec 16, 2025

Summary

Country flag images were not loading on Linux systems due to filesystem case sensitivity. The Angular components used toUpperCase() to build the image path (e.g., /assets/img/country-flag/US.svg), but most SVG files were stored in lowercase (e.g., us.svg).

This resulted in the error: Request is missing required HTTP header 'Token' because the static resource was not found, causing the rejection handler to return the API's missing token error instead.

Changes

  • Use toLowerCase() instead of toUpperCase() in flag-ip-fqdn component
  • Use toLowerCase() instead of toUpperCase() in exposure-service-pod-report-grid component
  • Rename 9 uppercase SVG files to lowercase for consistency:
    • AC.svgac.svg
    • BQ-BO.svgbq-bo.svg
    • BQ-SA.svgbq-sa.svg
    • BQ-SE.svgbq-se.svg
    • IC.svgic.svg
    • TA.svgta.svg
    • XA.svgxa.svg
    • XC.svgxc.svg
    • XO.svgxo.svg

The country flag images were not loading on Linux due to case sensitivity.
The Angular components used toUpperCase() to build the image path, but most
SVG files were lowercase (e.g., us.svg, fr.svg).

Changes:
- Use toLowerCase() instead of toUpperCase() in flag-ip-fqdn component
- Use toLowerCase() instead of toUpperCase() in exposure-service-pod-report-grid
- Rename 9 uppercase SVG files to lowercase for consistency:
  AC.svg, BQ-BO.svg, BQ-SA.svg, BQ-SE.svg, IC.svg, TA.svg, XA.svg, XC.svg, XO.svg
@gigi206 gigi206 requested a review from a team as a code owner December 16, 2025 19:53
@gigi206 gigi206 requested a review from gaktive December 16, 2025 19:53
@xingzhang-suse
Copy link
Collaborator

Hi @gigi206 ,

Thank you for your PR.
Actually, this issue was caused by a github file renaming issue, when we fix our case in #1091.

The new country flag picture names are uppercase. But when we replace the picture files, Github is not case sensitive.
So the most of the existing lowercase named files were not renamed as uppercase.
That's the reason of this issue.
We will submit another PR the fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants