Security Issue: Internal API URL and Token exposed in client code. #36

Closed
opened 2026-02-16 10:15:54 -05:00 by yindo · 1 comment
Owner

Originally created by @racerxdl on GitHub (Jul 15, 2024).

Currently the env APP_URL is getting exposed directly on client side because webpack adds it to the bundle. This is an issue because it exposed information about internal infrastructure and even the token for acessing the API directly.

Originally created by @racerxdl on GitHub (Jul 15, 2024). Currently the env APP_URL is getting exposed directly on client side because webpack adds it to the bundle. This is an issue because it exposed information about internal infrastructure and even the token for acessing the API directly.
yindo closed this issue 2026-02-16 10:15:54 -05:00
Author
Owner

@racerxdl commented on GitHub (Jul 15, 2024):

PS: This can be solved by removing the _PUBLIC prefix on the env variables (since they only need to be at backend side)

@racerxdl commented on GitHub (Jul 15, 2024): PS: This can be solved by removing the _PUBLIC prefix on the env variables (since they only need to be at backend side)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/webapp-conversation#36