问题描述
我最近实施精细上传，它的大部分很成功。一些用户却无法上传。他们都是使用的现代浏览器（IE10，FF和铬）。一个让我远程访问他们的机器，我能试试这两个浏览器和FF。
I recently implemented Fine Uploader and it's been mostly successful. A few users are however are not able to upload. They are all using modern browsers (IE10, FF and Chrome). One let me remotely access their machine and I was able to try it on both Chrome and FF.
我得到了两个同样的错误：
I got the same error on both:
[10:45:28.330] "[FineUploader 3.8.0] Received response status 403 with body: <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Invalid according to Policy: Policy expired.</Message><RequestId>--removed--</RequestId><HostId>--removed--</HostId></Error>"
它说的是与在它生成一个无效的政策，他们的计算机上的时区设置吗？
Is it something with the timezone settings on their computer where it's generating an invalid policy?
推荐答案
时区设置，不会有任何效果的时间为UTC。然而，如果时间在用户的计算机上是不准确的（例如，关5分钟以上），那么策略会过期，根据亚马逊
The timezone settings will have no effect as times are UTC. However, if the time on the user's computer is not accurate (say, off by 5 or more minutes), then the policy will be expired, according to Amazon.
精细上传设置截止日期为5分钟（同样，在UTC）。在浏览器中生成使用的日期，因此您的客户端计算机的时间将被使用。如果客户端设备的时钟是由5个或更多分钟缓慢，该策略将被看作是当亚马逊处理它过期。
Fine Uploader sets an expiration date to 5 minutes (again, in UTC). The date used is generated in the browser, so your client machine's time will be used. If the client machine's clock is slow by 5 or more minutes, the policy will be seen as expired when Amazon handles it.
我相当肯定，这个问题是由于在客户的计算机时钟显著漂移。如果验证这一点，我建议你指示他们保持系统时钟同步与时间服务器。
I'm fairly sure that the issue is due to a significant drift on your customer's machine clock. If you verify this, I suggest you instruct them to keep system clock synced with a time server.
这篇关于精细上传越来越＆QUOT;政策期满＆QUOT;消息发送到S3的一些的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！