<p>The catalog mode specifies how to expose layers and resources in the catalog that a user does not have privileges or via anonymous access.</p><p><strong>HIDE</strong> is the default mode and hides layers that the user does not have read access for. This is the most secure catalog mode. In the event the user has read but not write permissions this mode forces the layer to be read only. This mode excludes layers from the capabilities document that the user does not have read permissions for. Because of this this mode does not work very well with clients such as uDig or Google Earth, where authentication occurs only if the server returns a HTTP 401 after an attempt to access a secured layer.</p><p><strong>MIXED</strong> mode hides all layers the user does not have read permission for but triggers authentication for any other attempt to access the layer or its metadata directly. This mode is useful in cases where a layer is not to be advertised in a capabilities document, but select access to the layer may be granted to users (DataSecurityPage authentication) who are given direct access to the layer.</p><p><strong>CHALLENGE</strong> mode allows free access to layer metadata, but issues a 401 code triggering authentication for any attempt to access the layer data. This mode lists all layers in a service capabilities document and allows operations that return only metadata such as GetFeatureInfo and DescribeFeatureType without authentication. Any operation like GetMap or GetFeature that require actual data access result in a 401 code triggering authentication. This mode works well with capabilities driven clients such as uDig.</p>
<p>目录模式详细说明如何在目录中显示图层与资源使用户不可以拥有特权或匿名访问。</p><p><strong>隐藏</strong> 是对用户隐藏其没有访问权限的图层的默认模式。这是一个具有最高安全性的目录模式。在用户拥有读取但没有写入权限的状态下,该模式强制图层为只读。该模式在权限文档中排除用户没有访问权限的图层,因此这个模式在与只在请求受保护图层且服务器返回一个 HTTP 401 时发生授权事件的客户(如 uDig 和 Google Earth)并不能很好地合作。</p><p><strong>混合</strong>模式隐藏所有用户没有读取权限的图层但在任何其他请求访问图层或其元数据发生时激发授权。这种模式在一个图层没有被权限文档 mode hides all layers the user does not have read permission for but triggers authentication for any other attempt to access the layer or its metadata directly. This mode is useful in cases where a layer is not to be advertised in a capabilities document, but select access to the layer may be granted to users (DataSecurityPage authentication) who are given direct access to the layer.</p><p><strong>CHALLENGE</strong> mode allows free access to layer metadata, but issues a 401 code triggering authentication for any attempt to access the layer data. This mode lists all layers in a service capabilities document and allows operations that return only metadata such as GetFeatureInfo and DescribeFeatureType without authentication. Any operation like GetMap or GetFeature that require actual data access result in a 401 code triggering authentication. This mode works well with capabilities driven clients such as uDig.</p>
mode hides all layers the user does not have read permission for but triggers authentication for any other attempt to access the layer or its metadata directly. This mode is useful in cases where a layer is not to be advertised in a capabilities document, but select access to the layer may be granted to users (DataSecurityPage authentication) who are given direct access to the layer.</p><p><strong>CHALLENGE</strong> mode allows free access to layer metadata, but issues a 401 code triggering authentication for any attempt to access the layer data. This mode lists all layers in a service capabilities document and allows operations that return only metadata such as GetFeatureInfo and DescribeFeatureType without authentication. Any operation like GetMap or GetFeature that require actual data access result in a 401 code triggering authentication. This mode works well with capabilities driven clients such as uDig.</p>