{ "maintenance-mode": "维护模式", "maintenance-mode.help": "当论坛处在维护模式时,所有请求将被重定向到一个静态页面。管理员不受重定向限制,并可正常访问站点。", "maintenance-mode.status": "维护模式状态码", "maintenance-mode.message": "维护消息", "headers": "标题", "headers.allow-from": "设置 ALLOW-FROM 来放置 NodeBB 于 iFrame 中", "headers.csp-frame-ancestors": "Set Content-Security-Policy frame-ancestors header to Place NodeBB in an iFrame", "headers.csp-frame-ancestors-help": "'none', 'self'(default) or list of URIs to allow.", "headers.powered-by": "自定义由 NodeBB 发送的 \"Powered By\" 头部 ", "headers.acao": "Access-Control-Allow-Origin", "headers.acao-regex": "Access-Control-Allow-Origin 正则表达式", "headers.acao-help": "要拒绝所有网站,请留空", "headers.acao-regex-help": "输入正则表达式以匹配动态来源。要拒绝所有网站,请留空", "headers.acac": "Access-Control-Allow-Credentials", "headers.acam": "Access-Control-Allow-Methods", "headers.acah": "Access-Control-Allow-Headers", "hsts": "严格安全传输(HSTS)", "hsts.enabled": "启用HSTS(推荐)", "hsts.maxAge": "HSTS Max Age", "hsts.subdomains": "HSTS头信息包含的域名", "hsts.preload": "允许在HSTS头信息中预加载(preloading)", "hsts.help": "如果启用此项,站点将会向浏览器发送HSTS头信息。您可以设置是否为子域名开启HSTS,以及HSTS头信息中是否包含预加载标志(preload参数)如果您不了解HSTS,可以忽略此项设置。了解详情 ", "traffic-management": "流量管理", "traffic.help": "NodeBB 使用一个在高流量情况下自动拒绝请求的模块。尽管默认值就很棒,但您可以在这里调整这些设置。", "traffic.enable": "启用流量管理", "traffic.event-lag": "事件循环滞后阈值(毫秒)", "traffic.event-lag-help": "降低此值会减少页面加载的等待时间,但也会向更多用户显示“过载”消息。(需要重新启动)", "traffic.lag-check-interval": "检查间隔(毫秒)", "traffic.lag-check-interval-help": "降低此值会造成 NodeBB 的负载峰值变得更加敏感,但也可能导致检查变得过于敏感(需要重新启动)", "sockets.settings": "WebSocket 设置", "sockets.max-attempts": "最大重连尝试次数", "sockets.default-placeholder": "默认:%1", "sockets.delay": "重连等待时间", "analytics.settings": "分析设置", "analytics.max-cache": "分析缓存最大值", "analytics.max-cache-help": "On high-traffic installs, the cache could be exhausted continuously if there are more concurrent active users than the Max Cache value. (Restart required)", "compression.settings": "Compression Settings", "compression.enable": "Enable Compression", "compression.help": "This setting enables gzip compression. For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level. You can enable it here for testing purposes." }