keystonejs/keystone-classic

Make less files not publicly available

Open

#1,639 建立於 2015年9月2日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)JavaScript (14,656 star) (2,288 fork)batch import
bughelp wanted

描述

Every file under /public/styles/ is available through http when keystone is running.

Since *.less files could be considered as a part of the source code, could we move them to another location, e.g. /templates/styles/ to protect them from being available publicly?

It may be a good idea to keep /public/ folder only for files that are required during runtime, and keep source files elsewhere.

貢獻者指南

技術棧
javascriptnodejscss
領域
securitybackend
議題類型
security
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Keystone file structureLess CSSNode.js static serving
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Investigate the current file structure under /public/styles/ and /templates/ to understand how Keystone serves static assets. Identify all references to style files in the application (e.g., in templates, layout files, or server configuration) that would need updating after the move. Check if there are any existing mechanisms to prevent public access to certain file types, and consider if a more general solution (like a .htaccess or middleware) is preferred. Review any comments on the issue for maintainer guidance on the desired approach.
Make less files not publicly available · keystonejs/keystone-classic#1639 | Good First Issue