First, for security reasons, XML data can only be read from the same domain as the page.
第一，出于安全方面的原因，XML数据只能从与此页面相同的那个域中读取。
Check that the last condition, the security certificate has a valid name matching the name of the page you are trying to view, has a green checkmark associated with it.
检查最后一个条件，该安全证书有一个有效名称与您试图查看的页面名称相匹配，并且有一个绿色的选中标记与之相关联。
It is the recommended way of handling security, as explained previously in the notes accompanying the same page when creating an inbound FTP service.
正如前面在创建入站f TP服务时在同一页上附带的说明中所阐述的，这是处理安全性的建议方式。
The SOP is a security restriction that basically forbids a page loaded from a certain origin (meaning the protocol/host/port trio of the URL) to access data from a different origin.
SOP是一种安全性约束，它实际上禁止从某个源（即URL的协议/主机/端口三元组）装载的页面访问来自不同源的数据。
For the sake of security, the SOP makes a lot of sense because it doesn't allow a page from one origin to access, manipulate, and show data taken from another origin.
因 SOP不允许来自一个源头的页面访问、处理和显示来自另一个源头的数据，所以它对安全性很有意义。
The Internet cookie Report page of the Security Space Web site offers some frequency analysis through associating the cookie names with the server that issues them.
SecuritySpaceWeb网站的InternetcookieReport网页通过将这些cookie的名称和发行它们的服务器联合起来，从而提供了一些频率分析。
For more detailed information on creating a form-login page, see WebSphere Application Server v5 information center and look for the form login sub-section under the Security section.
有关创建表单登录页面的详细信息，请参阅WebSphereApplicationServerv 5informationcenter中安全部分下面的表单登录那一段。
On successful deployment, you can see "kerberos-realm" listed in the Security Realms page as shown in Figure 14.
如果部署成功，您将看到 “kerberos-realm”列示在SecurityRealms页面中，如图 14 所示。
Figure 4 shows the security constraint we defined for our form-login page
图4显示了在表单登录页面上定义的安全约束
Configuring a security constraint for the login page.
为登录页面配置安全约束。
The idea is to use SSL to provide security for a simple VNC viewer embedded in a Web page.
这种想法是使用SSL为嵌入在web页面中的一个简单vnc查看器提供安全性。
In the implemented solution, programmatic security is used to implement of a servlet that redirects users to an appropriate page upon successful authorization.
在已实现的解决方案中，程序性安全用于实现成功授权后将用户重定向至相应页面的servlet。
Be aware that WebSphere Application Server security fixes are usually rolled into the next cumulative fix for every supported release and then will no longer be listed on the recommend updates page.
请注意，对于每个支持的版本，WebSphereApplicationServer安全性修复通常会包含到下一个累积修复中，然后推荐更新页面中不再列出。
For portlet and page specific access control management, WebSphere Portal provides a comprehensive security management that lets you control user actions.
在Portlet和页面特定访问控制管理方面，WebSpherePortal提供全面的安全性管理，允许您控制用户操作。
Since the Rails framework is not involved if a page is in the cache, the server can't manage security for you.
如果页面已经在缓存内，那么就不会用到Rails框架，服务器并不能为您管理安全性。
The same domain problem, explained in more detail in Part 1 of this series, is a security limitation that restricts XMLHttp requests to the same server that delivered the original Web page.
本系列的第1部分详细讨论了同一域问题，出于安全上的考虑将XMLHttp请求限制到提供原始web页面的同一台服务器上。
A mashup application or page must address CSRF, Ajax vulnerabilities, XSS, and other potential security weaknesses.
mashup应用程序或页面必须解决CSRF、Ajax漏洞、XSS和其他潜在的安全漏洞。
If one page should not be cached, use "cache-control: no-cache, no-store" to make sure the page will not be cached, especially when the data involves security or sensitive information.
如果某个页面不应该被缓存，则使用“cache - control： no -cache, no -store”来确保该页面不会被缓存，尤其是当数据涉及安全或敏感信息时。
This code takes the ID of the AMI and the names of the key pair and security group selected in the form on the amis.php page.
以上代码提取amis.php页面表单中的AMI的ID和选中的密匙对以及安全组的名称。
HTML5 sandbox - a security feature to sandbox third party content on the website, to prevent malicious behavior like cookie stealing, form submission or page redirection.
HTML5SandBox——该安全特性可以将网站上的第三方内容放在沙箱当中，防止诸如Cookie窃取、表单提交或是页面重定向等恶意行为。
The values for the image ID, key name, and security group are passed to the manage_instance.php page via HTTP POST.
映像id、密匙名称和安全组的值通过HTTPPOST传递到manage _ instance. php页面。
Visit the OpenSSH Security page for details regarding older version-specific vulnerabilities (see the link in Resources later in this article).
访问OpenSSHSecurity网页以获得关于特定旧版本的缺陷的细节(请参阅本文后面的参考资料中的链接)。
According to the 2009 Security Threat Report [PDF] from Sophos, one new infected Web page is discovered every 4.5 seconds.
根据Sophos发布的《2009安全威胁报告》，每隔4.5秒就会有一个网页遭病毒感染。
You can also use the security Settings link on this page to bypass the wizard's default offer to set up the necessary code access security for your project.
也可使用该页面上的SecuritySettings链接以不使用向导提供的默认值，来为项目设置必要的代码访问安全性。
The Security page shown specifies the user rights for the advertisement.
Security页面指定广告的用户权限。
Since not just Web page requests, but potentially security-critical business requests are passing through port 80 now, increased vigilance is required.
因为现在不仅有web页面的请求而且还有潜在的强调安全的交易请求通过80端口传递，所以需要增强警惕性。
Use cases affected by this trade-off are RESTful URLs, bookmarking support, security through URL patterns, and page-flow validation, to mention a few.
受此影响的用例是RESTfulURL、书签支持、通过URL模式获得的安全性以及页面流验证等。
You can analyze your application to determine which permissions it needs by running the permission Calculator tool, accessible from the Security page of the Project Designer.
通过运行“权限计算器”工具(可从“项目设计器”的“安全”页访问)，可以对应用程序进行分析，以确定它需要的权限。
Security solution includes validating users, page authorization, reading and writing database using the password and manipulating database using store procedures.
安全性解决方案主要措施有用户验证、页面授权、密码存取数据库和使用存储过程操作数据库。
Security solution includes validating users, page authorization, reading and writing database using the password and manipulating database using store procedures.
安全性解决方案主要措施有用户验证、页面授权、密码存取数据库和使用存储过程操作数据库。
应用推荐