Main Views
QA Views
About Transvision
BETA
Displaying 37 results for the string Response in nb-NO:
Entity | nb-NO | en-US |
---|---|---|
Entity
#
all locales
devtools • client • har.properties har.responseBodyNotIncluded |
nb-NO
Response bodies are not included.
|
en-US
Response bodies are not included.
|
Entity
#
all locales
devtools • client • jsonview.properties jsonViewer.responseHeaders |
nb-NO
Response Headers
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties charts.totalCached |
nb-NO
Cached responses: %S
|
en-US
Cached responses: %S
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.audits.slowIconTooltip |
nb-NO
Slow server response time (%1$S). The recommended limit is %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 |
nb-NO
Copy Response
|
en-US
Copy Response
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.copyResponseHeaders |
nb-NO
Copy Response Headers
|
en-US
Copy Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.saveResponseAs |
nb-NO
Save Response As
|
en-US
Save Response As
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.headers.blockedByCORS |
nb-NO
Response body is not available to scripts (Reason: %S)
|
en-US
Response body is not available to scripts (Reason: %S)
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.tab.response |
nb-NO
Response
|
en-US
Response
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.toolbar.responseHeaders |
nb-NO
Response Headers
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.toolbar.responseTime |
nb-NO
Response Time
|
en-US
Response Time
|
Entity
#
all locales
devtools • client • netmonitor.properties responseCookies |
nb-NO
Response cookies
|
en-US
Response Cookies
|
Entity
#
all locales
devtools • client • netmonitor.properties responseEmptyText |
nb-NO
No response data available for this request
|
en-US
No response data available for this request
|
Entity
#
all locales
devtools • client • netmonitor.properties responseHeaders |
nb-NO
Response headers
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties responsePayload |
nb-NO
Response payload
|
en-US
Response Payload
|
Entity
#
all locales
devtools • client • netmonitor.properties responseTruncated |
nb-NO
Response has been truncated
|
en-US
Response has been truncated
|
Entity
#
all locales
dom • chrome • dom • dom.properties BadOpaqueInterceptionRequestModeWithURL |
nb-NO
Klarte ikke laste «%1$S». En ServiceWorker sendte en opaque Response til FetchEvent.respondWith() ved behandling av «%2$S» FetchEvent. Gjennomsiktige Response-objekter er bare gyldige når RequestMode er «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 |
nb-NO
Klarte ikke laste «%S». En ServiceWorker sendte en opaqueredirect Response til FetchEvent.respondWith() mens en ikke-navigasjons-FetchEvent ble behandlet.
|
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 CorsResponseForSameOriginRequest |
nb-NO
Klarte ikke å lese inn ‘%1$S’ ved å svare ‘%2$S’. En ServiceWorker kan ikke syntetisere et cors Response for en 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 |
nb-NO
Klarte ikke laste '%S'. En ServiceWorker sendte en Response med feil til FetchEvent.respondWith(). Dette betyr vanligvis at ServiceWorker utførte et ugyldig fetch()-kall.
|
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 |
nb-NO
Klarte ikke laste '%1$S'. En ServiceWorker sendte en promise til FetchEvent.respondWith() som resulterte i en ikke-Response-verdi '%2$S'.
|
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 |
nb-NO
Klarte ikke laste '%S'. En ServiceWorker sendte en brukt Response til FetchEvent.respondWith(). Kroppen til Response kan bare leses en gang. Bruk Response.clone() for å få tilgang til kroppen flere ganger.
|
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 |
nb-NO
Bruk av XMLHttpRequest sin responseType-attributt er ikke lenger støttet i synkron modus i vinduskonteksten.
|
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 |
nb-NO
The resource at “%1$S” was blocked by OpaqueResponseBlocking. Reason: “%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 SEC_ERROR_OCSP_BAD_SIGNATURE |
nb-NO
OCSP-responsen har en ugyldig signatur.
|
en-US
OCSP response has an invalid signature.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_FUTURE_RESPONSE |
nb-NO
OCSP-responsen er ikke gyldig ennå (inneholder en dato i fremtiden).
|
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_MALFORMED_RESPONSE |
nb-NO
Responsen fra OCSP-serveren var ødelagt eller ugyldig formatert.
|
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 |
nb-NO
OCSP-responsen inneholder utdatert informasjon.
|
en-US
The OCSP response contains out-of-date information.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_UNAUTHORIZED_RESPONSE |
nb-NO
Signereren av OCSP-responsen er ikke autorisert til å gi status for dette sertifikatet.
|
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 |
nb-NO
Klarte ikke dekode OCSP-responsen; den har ugyldig type.
|
en-US
The OCSP response cannot be fully decoded; it is of an unknown type.
|
Entity
#
all locales
toolkit • toolkit • contentanalysis • contentanalysis.ftl contentanalysis-genericresponse-message |
nb-NO
Innholdsanalyse svarte med { $response } for ressurs: { $content }
|
en-US
Content Analysis responded with { $response } for resource: { $content }
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-bad-signature |
nb-NO
OCSP-responsen har en ugyldig signatur.
|
en-US
OCSP response has an invalid signature.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-future-response |
nb-NO
OCSP-responsen er ikke gyldig ennå (inneholder en dato i fremtiden).
|
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-malformed-response |
nb-NO
Responsen fra OCSP-serveren var ødelagt eller ugyldig formatert.
|
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 |
nb-NO
OCSP-responsen inneholder utdatert informasjon.
|
en-US
The OCSP response contains out-of-date information.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-unauthorized-response |
nb-NO
Signereren av OCSP-responsen er ikke autorisert til å gi status for dette sertifikatet.
|
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 |
nb-NO
Klarte ikke dekode OCSP-responsen; den har ugyldig type.
|
en-US
The OCSP response cannot be fully decoded; it is of an unknown type.
|
Displaying 56 results for the string Response in en-US:
Entity | nb-NO | en-US |
---|---|---|
Entity
#
all locales
browser • pdfviewer • viewer.properties unexpected_response_error |
nb-NO
Uventet serverrespons.
|
en-US
Unexpected server response.
|
Entity
#
all locales
devtools • client • har.properties har.responseBodyNotIncluded |
nb-NO
Response bodies are not included.
|
en-US
Response bodies are not included.
|
Entity
#
all locales
devtools • client • jsonview.properties jsonViewer.responseHeaders |
nb-NO
Response Headers
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties charts.totalCached |
nb-NO
Cached responses: %S
|
en-US
Cached responses: %S
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.audits.slowIconTooltip |
nb-NO
Slow server response time (%1$S). The recommended limit is %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 |
nb-NO
Copy Response
|
en-US
Copy Response
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.copyResponseHeaders |
nb-NO
Copy Response Headers
|
en-US
Copy Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.saveResponseAs |
nb-NO
Save Response As
|
en-US
Save Response As
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.headers.blockedByCORS |
nb-NO
Response body is not available to scripts (Reason: %S)
|
en-US
Response body is not available to scripts (Reason: %S)
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.tab.response |
nb-NO
Response
|
en-US
Response
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.toolbar.responseHeaders |
nb-NO
Response Headers
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.toolbar.responseTime |
nb-NO
Response Time
|
en-US
Response Time
|
Entity
#
all locales
devtools • client • netmonitor.properties responseCookies |
nb-NO
Response cookies
|
en-US
Response Cookies
|
Entity
#
all locales
devtools • client • netmonitor.properties responseEmptyText |
nb-NO
No response data available for this request
|
en-US
No response data available for this request
|
Entity
#
all locales
devtools • client • netmonitor.properties responseHeaders |
nb-NO
Response headers
|
en-US
Response Headers
|
Entity
#
all locales
devtools • client • netmonitor.properties responsePayload |
nb-NO
Response payload
|
en-US
Response Payload
|
Entity
#
all locales
devtools • client • netmonitor.properties responseTruncated |
nb-NO
Response has been truncated
|
en-US
Response has been truncated
|
Entity
#
all locales
dom • chrome • dom • dom.properties BadOpaqueInterceptionRequestModeWithURL |
nb-NO
Klarte ikke laste «%1$S». En ServiceWorker sendte en opaque Response til FetchEvent.respondWith() ved behandling av «%2$S» FetchEvent. Gjennomsiktige Response-objekter er bare gyldige når RequestMode er «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 |
nb-NO
Klarte ikke laste «%S». En ServiceWorker sendte en opaqueredirect Response til FetchEvent.respondWith() mens en ikke-navigasjons-FetchEvent ble behandlet.
|
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 |
nb-NO
Feilet under lasting av "%S". En ServiceWorker passerte en redirigert respons til FetchEvent.respondWith() mens RedirectMode ikke er "follow".
|
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 |
nb-NO
Klarte ikke å lese inn ‘%1$S’ ved å svare ‘%2$S’. En ServiceWorker kan ikke syntetisere et cors Response for en 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 |
nb-NO
Klarte ikke laste '%S'. En ServiceWorker sendte en Response med feil til FetchEvent.respondWith(). Dette betyr vanligvis at ServiceWorker utførte et ugyldig fetch()-kall.
|
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 |
nb-NO
Klarte ikke laste '%1$S'. En ServiceWorker sendte en promise til FetchEvent.respondWith() som resulterte i en ikke-Response-verdi '%2$S'.
|
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 |
nb-NO
Klarte ikke laste '%S'. En ServiceWorker sendte en brukt Response til FetchEvent.respondWith(). Kroppen til Response kan bare leses en gang. Bruk Response.clone() for å få tilgang til kroppen flere ganger.
|
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 |
nb-NO
Bruk av XMLHttpRequest sin responseType-attributt er ikke lenger støttet i synkron modus i vinduskonteksten.
|
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 |
nb-NO
Forespørsel med kryssende opprinnelse ble blokkert: Same Origin-policyen tillater ikke lesing av den eksterne ressursen på %1$S. (Årsak: header «%2$S» er ikke tillatt i henhold til headeren «Access-Control-Allow-Headers» fra CORS preflight-svar).
|
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 |
nb-NO
Forespørsel med kryssende opprinnelse ble blokkert: Same Origin-policyen tillater ikke lesing av den eksterne ressursen på %1$S. (Årsak: CORS preflight-svar lyktes ikke). Statuskode: %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 |
nb-NO
Statuslinjen til HTTP-svaret er ugyldig
|
en-US
The status line of the HTTP response is invalid
|
Entity
#
all locales
netwerk • necko.properties ResourceBlockedORB |
nb-NO
The resource at “%1$S” was blocked by OpaqueResponseBlocking. Reason: “%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 |
nb-NO
OCSP-svaret inneholder ingen status for sertifikatet som blir kontrollert.
|
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 |
nb-NO
Serveren returnerte ugyldig HTTP-respons
|
en-US
Server returned bad HTTP response
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_BAD_LDAP_RESPONSE |
nb-NO
Serveren returnerte ugyldig LDAP-respons
|
en-US
Server returned bad LDAP response
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_CERT_NO_RESPONSE |
nb-NO
Cert-bibliotek: Ingen respons
|
en-US
Cert Library: No Response
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_BAD_SIGNATURE |
nb-NO
OCSP-responsen har en ugyldig signatur.
|
en-US
OCSP response has an invalid signature.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_FUTURE_RESPONSE |
nb-NO
OCSP-responsen er ikke gyldig ennå (inneholder en dato i fremtiden).
|
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 |
nb-NO
Ugyldig OCSP signerersertifikat i OCSP-respons.
|
en-US
Invalid OCSP signing certificate in OCSP response.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_MALFORMED_RESPONSE |
nb-NO
Responsen fra OCSP-serveren var ødelagt eller ugyldig formatert.
|
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 |
nb-NO
OCSP-responsen inneholder utdatert informasjon.
|
en-US
The OCSP response contains out-of-date information.
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_OCSP_UNAUTHORIZED_RESPONSE |
nb-NO
Signereren av OCSP-responsen er ikke autorisert til å gi status for dette sertifikatet.
|
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 |
nb-NO
Klarte ikke dekode OCSP-responsen; den har ugyldig type.
|
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 |
nb-NO
SSL-motparten klarte ikke motta en OCSP-respons for sertifikatet sitt.
|
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 |
nb-NO
Innholdsanalyse svarte med { $response } for ressurs: { $content }
|
en-US
Content Analysis responded with { $response } for resource: { $content }
|
Entity
#
all locales
toolkit • toolkit • neterror • certError.ftl unknownSocketType-title |
nb-NO
Uventet svar fra server
|
en-US
Unexpected response from server
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl mozilla-pkix-error-ocsp-response-for-cert-missing |
nb-NO
OCSP-svaret inneholder ingen status for sertifikatet som blir kontrollert.
|
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 |
nb-NO
Serveren returnerte ugyldig HTTP-respons
|
en-US
Server returned bad HTTP response
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-bad-ldap-response |
nb-NO
Serveren returnerte ugyldig LDAP-respons
|
en-US
Server returned bad LDAP response
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-cert-no-response |
nb-NO
Cert-bibliotek: Ingen respons
|
en-US
Cert Library: No Response
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-bad-signature |
nb-NO
OCSP-responsen har en ugyldig signatur.
|
en-US
OCSP response has an invalid signature.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-future-response |
nb-NO
OCSP-responsen er ikke gyldig ennå (inneholder en dato i fremtiden).
|
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 |
nb-NO
Ugyldig OCSP signerersertifikat i OCSP-respons.
|
en-US
Invalid OCSP signing certificate in OCSP response.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-malformed-response |
nb-NO
Responsen fra OCSP-serveren var ødelagt eller ugyldig formatert.
|
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 |
nb-NO
OCSP-responsen inneholder utdatert informasjon.
|
en-US
The OCSP response contains out-of-date information.
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl sec-error-ocsp-unauthorized-response |
nb-NO
Signereren av OCSP-responsen er ikke autorisert til å gi status for dette sertifikatet.
|
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 |
nb-NO
Klarte ikke dekode OCSP-responsen; den har ugyldig type.
|
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 |
nb-NO
SSL-motparten klarte ikke motta en OCSP-respons for sertifikatet sitt.
|
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 |
nb-NO
Uventet serverrespons.
|
en-US
Unexpected server response.
|
APIThese results are also available as an API request to search in
nb-NO or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.