使用 php css 文件是一个坏主意吗？
我只是想知道使用 php css 文件性能是好是坏。我真的很想做一个使用变量的php方法。
我所说的 php css 文件的意思是：
<?php header("Content-type: text/css"); ?>
你对此有何看法？
I just want to know if it's a good or bad idea to use a php css file performance wise. I really want to do a php method for the use of variables.
By php css file I mean:
<?php header("Content-type: text/css"); ?>
What are your thoughts on this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
不，这在野外相当常见。唯一的性能影响是动态输出文件时，可以通过服务器端（和客户端）缓存轻松缓解。
Nope, it's fairly common in the wild. The only performance hit is when you output the file dynamically, which can be mitigated easily with server-side (and client side) caching.
这是一个坏主意，但前提是您不缓存。
在服务器端，我希望您使用某种全局站点级变量，然后从中构建 CSS。好吧，只需确保保存文件，并在需要更改时使其失效（例如，从 SVN 签入）。
从客户端的角度来看，您希望确保不必在每次页面加载时都下载它。为此，您需要正确设置上次修改的标头或 Etag。
This is a bad idea, but only if you don't cache.
On the server side, I expect that you're using some sort of global site-level variables, then building your CSS from that. Fine, just make sure that you save the file, invalidating it whenever it needs to change (say, from an SVN checkin).
From the client's perspective, you want to ensure that it doesn't have to download it on every page load. For that you'll need to properly set last-modified headers or an Etag.
我认为这不是一个坏主意，而且我目前正在这样做。在我的框架中，我动态地将两个 css 组连接到两个单独的文件中，即站点主 CSS（布局、表单等）和一些特定于模块的 CSS（如果存在）。因此，它们可以单独缓存。我还使用 php vars 包含一些动态路径。
I don't think it's a bad idea, and I'm currently doing it in that way. In my framework I dynamically concatenate two css groups in two separate files, the site main CSSs (layout, forms, etc) and some module specific ones if they exists. So, they can be cached separately. I also include some dynamic path inside using php vars.