Main Views
QA Views
About Transvision
BETA
Displaying 10 results for the string Response in zh-TW:
Entity | zh-TW | en-US |
---|---|---|
Entity
#
all locales
dom • chrome • dom • dom.properties BadOpaqueInterceptionRequestModeWithURL |
zh-TW
「%1$S」載入失敗。有 ServiceWorker 在處理「%2$S」 FetchEvent 時傳送了 opaque Response 給 FetchEvent.respondWith()。Opaque Response 物件僅在 RequestMode 為「no-cors」時有效。
|
en-US
Failed to load ‘%1$S’. A ServiceWorker passed an opaque Response to FetchEvent.respondWith() while handling a ‘%2$S’ FetchEvent. Opaque Response objects are only valid when the RequestMode is ‘no-cors’.
|
Entity
#
all locales
dom • chrome • dom • dom.properties BadOpaqueRedirectInterceptionWithURL |
zh-TW
ServiceWorker 處理非瀏覽 FetchEvent 時傳送了 opaqueredirect Response 給 FetchEvent.respondWith(),「%S」載入失敗。
|
en-US
Failed to load ‘%S’. A ServiceWorker passed an opaqueredirect Response to FetchEvent.respondWith() while handling a non-navigation FetchEvent.
|
Entity
#
all locales
dom • chrome • dom • dom.properties BadRedirectModeInterceptionWithURL |
zh-TW
「%S」載入失敗。ServiceWorker 在 RedirectMode 不是「follow」的情況下傳送了被重導的 Response 給 FetchEvent.respondWith()。
|
en-US
Failed to load ‘%S’. A ServiceWorker passed a redirected Response to FetchEvent.respondWith() while RedirectMode is not ‘follow’.
|
Entity
#
all locales
dom • chrome • dom • dom.properties CorsResponseForSameOriginRequest |
zh-TW
無法回覆「%2$S」以載入「%1$S」。不允許 ServiceWorker 使用 cors Response 來合成 same-origin Request。
|
en-US
Failed to load ‘%1$S’ by responding ‘%2$S’. A ServiceWorker is not allowed to synthesize a cors Response for a same-origin Request.
|
Entity
#
all locales
dom • chrome • dom • dom.properties InterceptedErrorResponseWithURL |
zh-TW
ServiceWorker 傳送了 Error Response 給 FetchEvent.respondWith(),「%S」載入失敗。這通常代表 ServiceWorker 執行了無效的 fetch() 呼叫。
|
en-US
Failed to load ‘%S’. A ServiceWorker passed an Error Response to FetchEvent.respondWith(). This typically means the ServiceWorker performed an invalid fetch() call.
|
Entity
#
all locales
dom • chrome • dom • dom.properties InterceptedNonResponseWithURL |
zh-TW
「%1$S」載入失敗。ServiceWorker 傳送了 promise 給解出了非 Response 值「%2$S」的 FetchEvent.respondWith()。
|
en-US
Failed to load ‘%1$S’. A ServiceWorker passed a promise to FetchEvent.respondWith() that resolved with non-Response value ‘%2$S’.
|
Entity
#
all locales
dom • chrome • dom • dom.properties InterceptedUsedResponseWithURL |
zh-TW
ServiceWorker 傳送了使用過的 Response 給 FetchEvent.respondWith(),「%S」載入失敗。Response 的內容僅能讀取一次,若需要多次存取,請使用 Response.clone()。
|
en-US
Failed to load ‘%S’. A ServiceWorker passed a used Response to FetchEvent.respondWith(). The body of a Response may only be read once. Use Response.clone() to access the body multiple times.
|
Entity
#
all locales
dom • chrome • dom • dom.properties ResponseTypeSyncXHRWarning |
zh-TW
在同步模式的視窗內容當中,不再支援使用 XMLHttpRequest 當中的 responseType 屬性。
|
en-US
Use of XMLHttpRequest’s responseType attribute is no longer supported in the synchronous mode in window context.
|
Entity
#
all locales
netwerk • necko.properties ResourceBlockedORB |
zh-TW
位於「%1$S」的資源被 OpaqueResponseBlocking 封鎖,原因:「%2$S」。
|
en-US
The resource at “%1$S” was blocked by OpaqueResponseBlocking. Reason: “%2$S”.
|
Entity
#
all locales
toolkit • toolkit • contentanalysis • contentanalysis.ftl contentanalysis-genericresponse-message |
zh-TW
內容分析功能已對下列資源回覆 { $response }:{ $content }
|
en-US
Content Analysis responded with { $response } for resource: { $content }
|
Displaying 56 results for the string Response in en-US:
Entity | zh-TW | en-US |
---|---|---|
Entity
#
all locales
browser • pdfviewer • viewer.properties unexpected_response_error |
zh-TW
伺服器回應未預期的內容。
|
en-US
Unexpected server response.
|
Entity
#
all locales
devtools • client • har.properties har.responseBodyNotIncluded |
zh-TW
未包含回應內容。
|
en-US
Response bodies are not included.
|
Entity
#
all locales
devtools • client • jsonview.properties jsonViewer.responseHeaders |
zh-TW
回應標頭
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties charts.totalCached |
zh-TW
快取回應數: %S
|
en-US
Cached responses: %S
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.audits.slowIconTooltip |
zh-TW
伺服器回應緩慢(%1$S)。建議的時限為 %2$S。
|
en-US
Slow server response time (%1$S). The recommended limit is %2$S.
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.copyResponse |
zh-TW
複製回應內容
|
en-US
Copy Response
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.copyResponseHeaders |
zh-TW
複製回應標頭
|
en-US
Copy Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.saveResponseAs |
zh-TW
另存回覆內容
|
en-US
Save Response As
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.headers.blockedByCORS |
zh-TW
指令碼無法取得回應內容(原因:%S)
|
en-US
Response body is not available to scripts (Reason: %S)
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.tab.response |
zh-TW
回應
|
en-US
Response
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.toolbar.responseHeaders |
zh-TW
回應標頭
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.toolbar.responseTime |
zh-TW
回應時間
|
en-US
Response Time
|
Entity
#
all locales
devtools • client • netmonitor.properties responseCookies |
zh-TW
回應 cookie
|
en-US
Response Cookies
|
Entity
#
all locales
devtools • client • netmonitor.properties responseEmptyText |
zh-TW
此請求尚無回應資料
|
en-US
No response data available for this request
|
Entity
#
all locales
devtools • client • netmonitor.properties responseHeaders |
zh-TW
回應標頭
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties responsePayload |
zh-TW
回應酬載
|
en-US
Response Payload
|
Entity
#
all locales
devtools • client • netmonitor.properties responseTruncated |
zh-TW
回應已遭截斷
|
en-US
Response has been truncated
|
Entity
#
all locales
dom • chrome • dom • dom.properties BadOpaqueInterceptionRequestModeWithURL |
zh-TW
「%1$S」載入失敗。有 ServiceWorker 在處理「%2$S」 FetchEvent 時傳送了 opaque Response 給 FetchEvent.respondWith()。Opaque Response 物件僅在 RequestMode 為「no-cors」時有效。
|
en-US
Failed to load ‘%1$S’. A ServiceWorker passed an opaque Response to FetchEvent.respondWith() while handling a ‘%2$S’ FetchEvent. Opaque Response objects are only valid when the RequestMode is ‘no-cors’.
|
Entity
#
all locales
dom • chrome • dom • dom.properties BadOpaqueRedirectInterceptionWithURL |
zh-TW
ServiceWorker 處理非瀏覽 FetchEvent 時傳送了 opaqueredirect Response 給 FetchEvent.respondWith(),「%S」載入失敗。
|
en-US
Failed to load ‘%S’. A ServiceWorker passed an opaqueredirect Response to FetchEvent.respondWith() while handling a non-navigation FetchEvent.
|
Entity
#
all locales
dom • chrome • dom • dom.properties BadRedirectModeInterceptionWithURL |
zh-TW
「%S」載入失敗。ServiceWorker 在 RedirectMode 不是「follow」的情況下傳送了被重導的 Response 給 FetchEvent.respondWith()。
|
en-US
Failed to load ‘%S’. A ServiceWorker passed a redirected Response to FetchEvent.respondWith() while RedirectMode is not ‘follow’.
|
Entity
#
all locales
dom • chrome • dom • dom.properties CorsResponseForSameOriginRequest |
zh-TW
無法回覆「%2$S」以載入「%1$S」。不允許 ServiceWorker 使用 cors Response 來合成 same-origin Request。
|
en-US
Failed to load ‘%1$S’ by responding ‘%2$S’. A ServiceWorker is not allowed to synthesize a cors Response for a same-origin Request.
|
Entity
#
all locales
dom • chrome • dom • dom.properties InterceptedErrorResponseWithURL |
zh-TW
ServiceWorker 傳送了 Error Response 給 FetchEvent.respondWith(),「%S」載入失敗。這通常代表 ServiceWorker 執行了無效的 fetch() 呼叫。
|
en-US
Failed to load ‘%S’. A ServiceWorker passed an Error Response to FetchEvent.respondWith(). This typically means the ServiceWorker performed an invalid fetch() call.
|
Entity
#
all locales
dom • chrome • dom • dom.properties InterceptedNonResponseWithURL |
zh-TW
「%1$S」載入失敗。ServiceWorker 傳送了 promise 給解出了非 Response 值「%2$S」的 FetchEvent.respondWith()。
|
en-US
Failed to load ‘%1$S’. A ServiceWorker passed a promise to FetchEvent.respondWith() that resolved with non-Response value ‘%2$S’.
|
Entity
#
all locales
dom • chrome • dom • dom.properties InterceptedUsedResponseWithURL |
zh-TW
ServiceWorker 傳送了使用過的 Response 給 FetchEvent.respondWith(),「%S」載入失敗。Response 的內容僅能讀取一次,若需要多次存取,請使用 Response.clone()。
|
en-US
Failed to load ‘%S’. A ServiceWorker passed a used Response to FetchEvent.respondWith(). The body of a Response may only be read once. Use Response.clone() to access the body multiple times.
|
Entity
#
all locales
dom • chrome • dom • dom.properties ResponseTypeSyncXHRWarning |
zh-TW
在同步模式的視窗內容當中,不再支援使用 XMLHttpRequest 當中的 responseType 屬性。
|
en-US
Use of XMLHttpRequest’s responseType attribute is no longer supported in the synchronous mode in window context.
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowHeaderFromPreflight2 |
zh-TW
已封鎖跨來源請求: 同源政策不允許讀取 %1$S 的遠端資源。(原因: 根據 CORS preflight 回應的 'Access-Control-Allow-Headers' 內容,不允許使用檔頭「%2$S」)。
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: header ‘%2$S’ is not allowed according to header ‘Access-Control-Allow-Headers’ from CORS preflight response).
|
Entity
#
all locales
dom • chrome • security • security.properties CORSPreflightDidNotSucceed3 |
zh-TW
已封鎖跨來源請求: 同源政策不允許讀取 %1$S 的遠端資源。(原因: CORS preflight 回應並未成功)。狀態代碼: %2$S。
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS preflight response did not succeed). Status code: %2$S.
|
Entity
#
all locales
netwerk • necko.properties InvalidHTTPResponseStatusLine |
zh-TW
HTTP 回應的狀態行無效
|
en-US
The status line of the HTTP response is invalid
|
Entity
#
all locales
netwerk • necko.properties ResourceBlockedORB |
zh-TW
位於「%1$S」的資源被 OpaqueResponseBlocking 封鎖,原因:「%2$S」。
|
en-US
The resource at “%1$S” was blocked by OpaqueResponseBlocking. Reason: “%2$S”.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING |
zh-TW
OCSP 回應中並未包含要驗證的憑證的狀態。
|
en-US
The OCSP response does not include a status for the certificate being verified.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_BAD_HTTP_RESPONSE |
zh-TW
伺服器回覆了無效的 HTTP 回應
|
en-US
Server returned bad HTTP response
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_BAD_LDAP_RESPONSE |
zh-TW
伺服器回覆了無效的 LDAP 回應
|
en-US
Server returned bad LDAP response
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_CERT_NO_RESPONSE |
zh-TW
憑證函式庫: 無回應
|
en-US
Cert Library: No Response
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_BAD_SIGNATURE |
zh-TW
OCSP 回應含無效的簽章。
|
en-US
OCSP response has an invalid signature.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_FUTURE_RESPONSE |
zh-TW
OCSP 回應尚未生效(內含未來的日期)。
|
en-US
The OCSP response is not yet valid (contains a date in the future).
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_INVALID_SIGNING_CERT |
zh-TW
OCSP 回應含無效的 OCSP 簽署憑證。
|
en-US
Invalid OCSP signing certificate in OCSP response.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_MALFORMED_RESPONSE |
zh-TW
從 OCSP 伺服器傳來的回應已損毀或格式不正確。
|
en-US
The response from the OCSP server was corrupted or improperly formed.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_OLD_RESPONSE |
zh-TW
OCSP 回應內含過期的資訊。
|
en-US
The OCSP response contains out-of-date information.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_UNAUTHORIZED_RESPONSE |
zh-TW
OCSP 回應的簽署者未獲授權回應此憑證的狀態。
|
en-US
The signer of the OCSP response is not authorized to give status for this certificate.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_UNKNOWN_RESPONSE_TYPE |
zh-TW
OCSP 回應無法被完全解碼;回應是未知的類型。
|
en-US
The OCSP response cannot be fully decoded; it is of an unknown type.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_BAD_CERT_STATUS_RESPONSE_ALERT |
zh-TW
SSL 端點無法取得其憑證的 OCSP 回應。
|
en-US
SSL peer was unable to get an OCSP response for its certificate.
|
Entity
#
all locales
toolkit • toolkit • contentanalysis • contentanalysis.ftl contentanalysis-genericresponse-message |
zh-TW
內容分析功能已對下列資源回覆 { $response }:{ $content }
|
en-US
Content Analysis responded with { $response } for resource: { $content }
|
Entity
#
all locales
toolkit • toolkit • neterror • certError.ftl unknownSocketType-title |
zh-TW
伺服器回應錯誤
|
en-US
Unexpected response from server
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl mozilla-pkix-error-ocsp-response-for-cert-missing |
zh-TW
OCSP 回應中並未包含要驗證的憑證的狀態。
|
en-US
The OCSP response does not include a status for the certificate being verified.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-bad-http-response |
zh-TW
伺服器回覆了無效的 HTTP 回應
|
en-US
Server returned bad HTTP response
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-bad-ldap-response |
zh-TW
伺服器回覆了無效的 LDAP 回應
|
en-US
Server returned bad LDAP response
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-cert-no-response |
zh-TW
憑證函式庫: 無回應
|
en-US
Cert Library: No Response
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-bad-signature |
zh-TW
OCSP 回應含無效的簽章。
|
en-US
OCSP response has an invalid signature.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-future-response |
zh-TW
OCSP 回應尚未生效(內含未來的日期)。
|
en-US
The OCSP response is not yet valid (contains a date in the future).
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-invalid-signing-cert |
zh-TW
OCSP 回應含無效的 OCSP 簽署憑證。
|
en-US
Invalid OCSP signing certificate in OCSP response.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-malformed-response |
zh-TW
從 OCSP 伺服器傳來的回應已損毀或格式不正確。
|
en-US
The response from the OCSP server was corrupted or improperly formed.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-old-response |
zh-TW
OCSP 回應內含過期的資訊。
|
en-US
The OCSP response contains out-of-date information.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-unauthorized-response |
zh-TW
OCSP 回應的簽署者未獲授權回應此憑證的狀態。
|
en-US
The signer of the OCSP response is not authorized to give status for this certificate.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-unknown-response-type |
zh-TW
OCSP 回應無法被完全解碼;回應是未知的類型。
|
en-US
The OCSP response cannot be fully decoded; it is of an unknown type.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl ssl-error-bad-cert-status-response-alert |
zh-TW
SSL 端點無法取得其憑證的 OCSP 回應。
|
en-US
SSL peer was unable to get an OCSP response for its certificate.
|
Entity
#
all locales
toolkit • toolkit • pdfviewer • viewer.ftl pdfjs-unexpected-response-error |
zh-TW
伺服器回應未預期的內容。
|
en-US
Unexpected server response.
|
APIThese results are also available as an API request to search in
zh-TW or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.