blocks|key|2445950|text|有几种方法，每一种都有缺点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2445951|与静态CSS文件不同，您可以通过模板(或其他一些将资源映射到CloudFront位置的智能方法)生成它。通过使用Last-Modified和max-age缓存头，您可以在这里使用一定程度的缓存。最难的解决方案，但可以说是最好的保护。|2445952|为所有CSS资源设置一个重定向路径，基本上是一个小脚本来重写CF的路径(注意只重写CSS资源，不重写其他内容)。这允许您保留当前的静态CSS，但会打开重定向脚本的潜在热链接。|2445953|介于这两者之间的东西可能是cron脚本，它会生成带有链接的静态CSS文件，该文件将在1.5天内过期，以减少服务器负载。|2445954|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

There are a few way, each with drawbacks. 

Instead of a static CSS file, you generate it off a template (or some other smart way to map resources to CloudFront locations). You can use some degree of caching here by using Last-Modified and max-age Cache headers. The hardest solution but arguably the best protection. 

Set up a redirection path for all your CSS resources, basically a small script that rewrites the path to CF (take care to only rewrite CSS resources and nothing else). This allows you to keep your current static CSS but opens up a potential hot linking of your redirection script. 

Something in between could be a cron script that generates static CSS files with links that expire in 1.5d) to reduce server load.

blocks|key|4172745|text|您可以每隔一两天轮换整个CDN主机名，这样就不必更改css中的任何内容(假设css位于示例中所示的CDN上)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4172746|http://www.explainthatstuff.com/blocking-cloudfront-hotlinks.html|offset|length|4172747|然后你的CSS不需要签名的URL，你仍然可以同样有效地阻止热链接。|4172748|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1T|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

you could rotate the entire CDN host name every day or two, then you don't have to change anything in the css (assuming the css is on the CDN which it looks like from the example)

<a href="http://www.explainthatstuff.com/blocking-cloudfront-hotlinks.html" rel="nofollow">http://www.explainthatstuff.com/blocking-cloudfront-hotlinks.html</a>

Then your CSS doesn't need signed URLs and you can still block hotlinking just as effectively.

blocks|key|4172781|text|在yr中使用<base>标签怎么样？虽然没有尝试，但可能会有所帮助。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4172782|另一种选择是使用php生成样式表。例如，您获得了所有图像的已签名urls，然后将它们作为变量推送到样式元素。|4172783|entityMap^0|6|6|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

how about using <code>&lt;base&gt;</code> tag in yr html?
Though did'nt try, but might help.

Another option is to use php to generate your stylesheet. for example, you get the signed urls for all the images, then you push them as variables to the style elements.

blocks|key|2277284|text|让我后退一步，问一个基本的问题:你真的担心人们热链接你的图片吗？真的？如果有人这样做了，它会对你产生什么样的现实影响？真的？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2277285|如果你有一个合法的理由来阻止人们热链接，那么我不太确定any+CDN服务(在这个例子中是CloudFront)对你来说是正确的解决方案。|offset|length|style|BOLD|2277286|嘿，我只是说实话，…|2277287|entityMap^0|0|R|3|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Let me step back and ask a fundamental question: Are you really worried about people hotlinking your images? Really? And if someone does, what is the realistic impact it will have on you? Really?

If you have a legitimate reason for preventing people from hot linking, then I'm not really sure that any CDN service (in this case, CloudFront) is the right solution for you.

Hey, I'm just being honest…

blocks|key|4172852|text|对css文件使用私有发行版通常是一个非常糟糕的主意，因为向css添加(可能不断变化的)过期时间和签名会阻止浏览器缓存它们，因此首先会大大降低使用Cloudfront的有用性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4172853|即使你使用很长的过期时间，那么那些拼命想要热链接你的css背景图像的人会简单地设置一个脚本来抓取你的css文件并从那里提取图像urls。|4172854|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It's generally a really bad idea to use private distributions for your css files, because adding the (presumably constantly changing) expiration time and signature to css urls prevents browsers from caching them, therefore greatly reducing the usefulness of using Cloudfront in the first place.

And even if you use long expiration times, then someone who desperately wants to hotlink your css background images will simply set up a script to scrape your css file and extract the image urls from there.

blocks|key|2446203|text|我最近听说了将base64编码成html/css。这有好处也有坏处，但这可能就是你想要的：Is+embedding+background+image+data+into+CSS+as+Base64+good+or+bad+practice?|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2446204|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1124149/is-embedding-background-image-data-into-css-as-base64-good-or-bad-practice^0|19|23|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I just recently heard about base64 encoding into html/css. There are pros and cons, but it might be what your looking for:
<a href="https://stackoverflow.com/questions/1124149/is-embedding-background-image-data-into-css-as-base64-good-or-bad-practice">Is embedding background image data into CSS as Base64 good or bad practice?</a>

I created a private distribution in Cloudfront to prevent hotlinking. I managed to create links to my objects with signed URL which is working fine now.

My only concerns, is that images link inside my css stylesheets are not working because they are not signed. So if I have, for instance:

<pre><code>background-image: url('../img/bg.png');
</code></pre>

The background image is not going to show up since the stylesheet does not include a signed url, and therefore, Cloudfront refuses to serve the content.

Is there anything I can do to prevent this ?

Amazon Cloudfront private distribution - links to images inside CSS

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在Cloudfront中创建了一个私有发行版，以防止热链接。我设法用带签名的URL创建了到我的对象的链接，现在工作得很好。我唯一担心的是，我的css样式表中的图像链接不起作用，因为它们没有签名。所以如果我有，举个例子：background-image: url('../img/bg.png');背景图像不会显示出来，...

问Amazon Cloudfront私有分发- CSS中的图像链接
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Amazon Cloudfront私有分发- CSS中的图像链接EN