Main Views
QA Views
About Transvision
BETA
Displaying 21 results for the string header in nn-NO:
| Entity | nn-NO | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
nn-NO
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
nn-NO
Freistnad på å setje ein forboden header vart avslått: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncErrorFramePlain |
nn-NO
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSAllowHeaderFromPreflightDeprecation |
nn-NO
Cross-Origin Request Warning: The Same Origin Policy will disallow reading the remote resource at %1$S soon. (Reason: When the `Access-Control-Allow-Headers` is `*`, the `Authorization` header is not covered. To include the `Authorization` header, it must be explicitly listed in CORS header `Access-Control-Allow-Headers`).
|
en-US
Cross-Origin Request Warning: The Same Origin Policy will disallow reading the remote resource at %1$S soon. (Reason: When the `Access-Control-Allow-Headers` is `*`, the `Authorization` header is not covered. To include the `Authorization` header, it must be explicitly listed in CORS header `Access-Control-Allow-Headers`).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSAllowOriginNotMatchingOrigin |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: CORS-header 'Access-Control-Allow-Origin' er ikkje '%2$S')
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘%2$S’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowHeaderFromPreflight2 |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: header «%2$S» er ikkje tillaten i forhold til headeren «Access-Control-Allow-Headers» frå 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 CORSMissingAllowOrigin2 |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: CORS-header «Access-Control-Allow-Origin» manglar). Statuskode: %2$S.
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: %2$S.
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMultipleAllowOriginNotAllowed |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: fleire CORS-header ‘Access-Control-Allow-Origin’ ikkje tillate).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSOriginHeaderNotAdded |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: CORS-header «Origin» kan ikkje leggjast til).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Origin’ cannot be added).
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReferrerLengthOverLimitation |
nn-NO
HTTP Referrer header: Lengda er over grensa på «%1$S» byte - reduserer referrer header ned til opphav: «%2$S»
|
en-US
HTTP Referrer header: Length is over “%1$S” bytes limit - stripping referrer header down to origin: “%2$S”
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReferrerOriginLengthOverLimitation |
nn-NO
HTTP Referrer header: Lengda for opphav innen referrer er over grensa på «%1$S» byte - fjernar referrer med opphav: «%2$S».
|
en-US
HTTP Referrer header: Length of origin within referrer is over “%1$S” bytes limit - removing referrer with origin “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties RunningClearSiteDataValue |
nn-NO
Clear-Site-Data header tvinga opprydding av “%S” data.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som ikkje kunne tolkast.
|
en-US
Strict-Transport-Security: The site specified a header that could not be parsed successfully.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSInvalidIncludeSubdomains |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som inneheldt eit ugyldig 'includeSubDomains'-direktiv.
|
en-US
Strict-Transport-Security: The site specified a header that included an invalid ‘includeSubDomains’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSInvalidMaxAge |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som inneheldt eit ugyldig 'max-age'-direktiv.
|
en-US
Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleIncludeSubdomains |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som inneheldt fleire 'includeSubDomains'-direktiv.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som inneheldt fleire 'max-age'-direktiv.\u0020
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘max-age’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSNoMaxAge |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som ikkje inneheldt eit 'max-age'-direktiv.
|
en-US
Strict-Transport-Security: The site specified a header that did not include a ‘max-age’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties UnknownClearSiteDataValue |
nn-NO
Clear-Site-Data header funne. Ukjend verdi “%S”.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties XCTOHeaderValueMissing |
nn-NO
X-Content-Type-Options header-åtvaring: verdien var “%1$S”; meinte du å senda “nosniff”?
|
en-US
X-Content-Type-Options header warning: value was “%1$S”; did you mean to send “nosniff”?
|
|
Entity
#
all locales
dom • chrome • security • security.properties XFrameOptionsInvalid |
nn-NO
Ein ugyldig X-Frame-Options-header vart funnen under innlesing av «%1$S»: «%2$S» er ikkje eit gyldig direktiv.
|
en-US
Invalid X-Frame-Options header was found when loading “%2$S”: “%1$S” is not a valid directive.
|
Displaying 57 results for the string header in en-US:
| Entity | nn-NO | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
nn-NO
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheader |
nn-NO
kolonneoverskrift
|
en-US
column header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties header |
nn-NO
topptekst
|
en-US
header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheader |
nn-NO
radoverskrift
|
en-US
row header
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
nn-NO
Freistnad på å setje ein forboden header vart avslått: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadCryptoKeyHeader |
nn-NO
ServiceWorker for området ‘%1$S’ feila med å dekryptere ei push-melding. Headarern ‘Crypto-Key‘ må inkludere eit ‘dh‘-parameter som inneheld den offentlege nøkkelen til apptenaren. Sjå https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for meir informasjon.
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Crypto-Key‘ header must include a ‘dh‘ parameter containing the app server’s public key. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadEncodingHeader |
nn-NO
ServiceWorker for området ‘%1$S’ feila med å dekryptera ei push-melding. Headern ‘Content-Encoding‘ må vera ‘aesgcm‘. ‘Aesgcm128‘ er tillate, men forelda og vil snart fjernast. Sjå https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 for meir informasjon.
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Content-Encoding‘ header must be ‘aesgcm‘. ‘aesgcm128‘ is allowed, but deprecated and will soon be removed. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadEncryptionHeader |
nn-NO
ServiceWorkeren for området ‘%1$S’ klarte ikkje å dekryptere ei push-melding. 'Encryption'-headeren må innehalde eit unikt 'salt'-parameter for kvar melding. Sjå https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for meir informasjon.
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Encryption’ header must include a unique ‘salt‘ parameter for each message. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadEncryptionKeyHeader |
nn-NO
ServiceWorker för område ‘%1$S’ feila med ådekryptera ei push-melding. Headern ‘Encryption-Key’ må innehalde ein ‘dh‘-parameter. Denne headeren er forelda og vil snaart fjernast. Bruk ‘Crypto-Key‘ med ‘Content-Encoding: aesgcm‘ i staden. Sjå https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for meir informasjon.
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Encryption-Key’ header must include a ‘dh‘ parameter. This header is deprecated and will soon be removed. Please use ‘Crypto-Key‘ with ‘Content-Encoding: aesgcm‘ instead. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadRecordSize |
nn-NO
ServiceWorkeren for området ‘%1$S’ klarte ikkje å dekryptere ei push-melding. 'rs'-parameteret til 'Encryption'-headeren må vere mellom %2$S og 2^36-31, eller utelaten heilt. Sjå https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for meir informasjon.
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘rs‘ parameter of the ‘Encryption‘ header must be between %2$S and 2^36-31, or omitted entirely. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadSalt |
nn-NO
ServiceWorker for området ‘%1$S’ feila med å dekryptera ei push-melding. Parametern 'salt' i headern 'Encryption' må vera base64url-kodad (https://tools.ietf.org/html/rfc7515#appendix-C) og vera minst 16 byte før kodning. Sjå https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for meir informasjon.
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘salt‘ parameter in the ‘Encryption‘ header must be base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C), and be at least 16 bytes before encoding. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadSenderKey |
nn-NO
ServiceWorker for området ‘%1$S’ feila med å dekryptere ei push-melding. Parameteren 'dh' i headern 'Crypto-Key' må vere appserveren Diffie-Hellman sin offentlege nøkkel, base64url-koda (https://tools.ietf.org/html/rfc7515#appendix-C) og i forma «uncompressed» eller «raw» (65 byte før kodning). Sjå https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for meir informasjon.
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘dh‘ parameter in the ‘Crypto-Key‘ header must be the app server’s Diffie-Hellman public key, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C) and in “uncompressed” or “raw” form (65 bytes before encoding). See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties ServiceWorkerScopePathMismatch |
nn-NO
Klarte ikkje å registrere ein ServiceWorker: Søkjestien til området '%1$S' er ikkje under det maksimale området som er tillate '%2$S'. Juster området, flytt skriptet for ServiceWorker eller bruk Service-Worker-Allowed HTTP-hovudet for å tillate området.
|
en-US
Failed to register a ServiceWorker: The path of the provided scope ‘%1$S’ is not under the max scope allowed ‘%2$S’. Adjust the scope, move the Service Worker script, or use the Service-Worker-Allowed HTTP header to allow the scope.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncDetectorReload |
nn-NO
Teiknkodinga til dokumentet vart ikkje deklarert, og kodinga var kun mogleg å gjette ut frå innhaldet seint. Dette gjorde at dokumentet vart lasta på nytt. Teiknkodinga må deklarerast i Content-Type HTTP-headeren, ved å bruke ein meta-tag eller ved å bruke eit byte-rekkjefølgjemerke.
|
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncDetectorReloadPlain |
nn-NO
Teiknkodinga til dokumentet vart ikkje deklarert, og kodinga var kun mogleg å gjette ut frå innhaldet seint. Dette gjorde at dokumentet vart lasta på nytt. Teiknkodinga må deklarerast i Content-Type HTTP-headeren eller ved å bruke eit byte-rekkjefølgjemerke.
|
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncErrorFrame |
nn-NO
Bytestraumen var feil i høve til teiknkodinga som vart arva frå det overordna dokumentet. Teiknkodinga må deklarerast i Content-Type HTTP-headeren, ved å bruke ein meta-tag eller ved å bruke eit byte-rekkjefølgjemerke.
|
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncErrorFramePlain |
nn-NO
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncNoDecl |
nn-NO
Teiknkodinga til dokumentet vart ikkje deklarert, så kodinga vart gjetta ut frå innhaldet. Teiknkodinga må deklarerast i Content-Type HTTP-headeren, ved å bruke ein meta-tag eller ved å bruke eit byte-rekkjefølgjemerke.
|
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncNoDeclPlain |
nn-NO
Teiknkodinga til dokumentet vart ikkje deklarert, så kodinga vart gjetta ut frå innhaldet. Teiknkodinga må deklarerast i Content-Type HTTP-headeren eller ved å bruke eit byte-rekkjefølgjemerke.
|
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSAllowHeaderFromPreflightDeprecation |
nn-NO
Cross-Origin Request Warning: The Same Origin Policy will disallow reading the remote resource at %1$S soon. (Reason: When the `Access-Control-Allow-Headers` is `*`, the `Authorization` header is not covered. To include the `Authorization` header, it must be explicitly listed in CORS header `Access-Control-Allow-Headers`).
|
en-US
Cross-Origin Request Warning: The Same Origin Policy will disallow reading the remote resource at %1$S soon. (Reason: When the `Access-Control-Allow-Headers` is `*`, the `Authorization` header is not covered. To include the `Authorization` header, it must be explicitly listed in CORS header `Access-Control-Allow-Headers`).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSAllowOriginNotMatchingOrigin |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: CORS-header 'Access-Control-Allow-Origin' er ikkje '%2$S')
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘%2$S’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSInvalidAllowHeader |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: ugyldig verdi '%2$S' i CORS-headeren 'Access-Control-Allow-Headers').
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: invalid token ‘%2$S’ in CORS header ‘Access-Control-Allow-Headers’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSInvalidAllowMethod |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: ugyldig verdi '%2$S' i CORS-headeren 'Access-Control-Allow-Methods').
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: invalid token ‘%2$S’ in CORS header ‘Access-Control-Allow-Methods’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMethodNotFound |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: Fann ikkje metoden i CORS-headeren 'Access-Control-Allow-Methods').
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowCredentials |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: venta 'true' i CORS-headeren 'Access-Control-Allow-Credentials').
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowHeaderFromPreflight2 |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: header «%2$S» er ikkje tillaten i forhold til headeren «Access-Control-Allow-Headers» frå 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 CORSMissingAllowOrigin2 |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: CORS-header «Access-Control-Allow-Origin» manglar). Statuskode: %2$S.
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: %2$S.
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMultipleAllowOriginNotAllowed |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: fleire CORS-header ‘Access-Control-Allow-Origin’ ikkje tillate).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSNotSupportingCredentials |
nn-NO
Cross-Origin-førespurnad vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på '%1$S'. (Årsak: Påloggingsdetaljar vert ikkje støtta dersom CORS-headeren ‘Access-Control-Allow-Origin’ er ‘*’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at ‘%1$S’. (Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSOriginHeaderNotAdded |
nn-NO
Førespurnad med kryssande opphav vart blokkert: Same Origin-policyen tillèt ikkje lesing av den eksterne ressursen på %1$S. (Årsak: CORS-header «Origin» kan ikkje leggjast til).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Origin’ cannot be added).
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReferrerLengthOverLimitation |
nn-NO
HTTP Referrer header: Lengda er over grensa på «%1$S» byte - reduserer referrer header ned til opphav: «%2$S»
|
en-US
HTTP Referrer header: Length is over “%1$S” bytes limit - stripping referrer header down to origin: “%2$S”
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReferrerOriginLengthOverLimitation |
nn-NO
HTTP Referrer header: Lengda for opphav innen referrer er over grensa på «%1$S» byte - fjernar referrer med opphav: «%2$S».
|
en-US
HTTP Referrer header: Length of origin within referrer is over “%1$S” bytes limit - removing referrer with origin “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderDuplicateGroup |
nn-NO
Rapporteringshovud: ignorerer duplisert gruppe med namnet "%S".
|
en-US
Reporting Header: ignoring duplicated group named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidEndpoint |
nn-NO
Rapporteringshovud: ignorerer ugyldig sluttpunkt for objekt som heiter "%S".
|
en-US
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidItem |
nn-NO
Rapporteringshovud: ignorerer ogyldig objekt med namnet "%S".
|
en-US
Reporting Header: ignoring invalid item named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidJSON |
nn-NO
Rapporteringshovud: ugyldig JSON-verdi motteken.
|
en-US
Reporting Header: invalid JSON value received.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidNameItem |
nn-NO
Rapporteringshovud: ugyldig namn for gruppe.
|
en-US
Reporting Header: invalid name for group.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidURLEndpoint |
nn-NO
Rapporteringshovud: ignorerer ugyldig sluttpunktsadresse "%1$S" for objekt som heiter "%2$S".
|
en-US
Reporting Header: ignoring invalid endpoint URL “%1$S” for item named “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties RunningClearSiteDataValue |
nn-NO
Clear-Site-Data header tvinga opprydding av “%S” data.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som ikkje kunne tolkast.
|
en-US
Strict-Transport-Security: The site specified a header that could not be parsed successfully.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSInvalidIncludeSubdomains |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som inneheldt eit ugyldig 'includeSubDomains'-direktiv.
|
en-US
Strict-Transport-Security: The site specified a header that included an invalid ‘includeSubDomains’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSInvalidMaxAge |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som inneheldt eit ugyldig 'max-age'-direktiv.
|
en-US
Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleIncludeSubdomains |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som inneheldt fleire 'includeSubDomains'-direktiv.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som inneheldt fleire 'max-age'-direktiv.\u0020
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘max-age’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSNoMaxAge |
nn-NO
Strict-Transport-Security: Nettstaden spesifiserte ein header som ikkje inneheldt eit 'max-age'-direktiv.
|
en-US
Strict-Transport-Security: The site specified a header that did not include a ‘max-age’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSUnknownError |
nn-NO
Strict-Transport-Security: Ein ukjend feil oppstod ved behandling av headeren spesifisert av nettstaden.
|
en-US
Strict-Transport-Security: An unknown error occurred processing the header specified by the site.
|
|
Entity
#
all locales
dom • chrome • security • security.properties UnknownClearSiteDataValue |
nn-NO
Clear-Site-Data header funne. Ukjend verdi “%S”.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties XCTOHeaderValueMissing |
nn-NO
X-Content-Type-Options header-åtvaring: verdien var “%1$S”; meinte du å senda “nosniff”?
|
en-US
X-Content-Type-Options header warning: value was “%1$S”; did you mean to send “nosniff”?
|
|
Entity
#
all locales
dom • chrome • security • security.properties XFrameOptionsInvalid |
nn-NO
Ein ugyldig X-Frame-Options-header vart funnen under innlesing av «%1$S»: «%2$S» er ikkje eit gyldig direktiv.
|
en-US
Invalid X-Frame-Options header was found when loading “%2$S”: “%1$S” is not a valid directive.
|
|
Entity
#
all locales
netwerk • necko.properties CORPBlocked |
nn-NO
Ressursen på «%1$S» vart blokkert på grunn av headeren Cross-Origin-Resource-Policy (eller mangel på den). Sjå %2$S
|
en-US
The resource at “%1$S” was blocked due to its Cross-Origin-Resource-Policy header (or lack thereof). See %2$S
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties customHeaderFooterPrompt |
nn-NO
Skriv inn eigen topp/botn-tekst
|
en-US
Please enter your custom header/footer text
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties headerFooter |
nn-NO
Topp- og botntekst
|
en-US
Header and Footer
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl advanced-tab.label |
nn-NO
Margar og topp/botn-tekstar
|
en-US
Margins & Header/Footer
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl custom-prompt-prompt |
nn-NO
Skriv inn eigen topp/botn-tekst
|
en-US
Enter your custom header/footer text
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-center-tip.tooltiptext |
nn-NO
Midtstilt topptekst
|
en-US
Center header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-left-tip.tooltiptext |
nn-NO
Venstre topptekst
|
en-US
Left header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-right-tip.tooltiptext |
nn-NO
Høgre topptekst
|
en-US
Right header
|
APIThese results are also available as an API request to search in
nn-NO or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.