Main Views
QA Views
About Transvision
BETA
Displaying 45 results for the string header in fi:
Entity | fi | en-US |
---|---|---|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
fi
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
fi
Attempt to set a forbidden header was denied: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadCryptoKeyHeader |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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 |
fi
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.
|
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 |
fi
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.
|
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 CORSAllowOriginNotMatchingOrigin |
fi
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').
|
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 |
fi
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').
|
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 |
fi
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').
|
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 |
fi
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').
|
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 |
fi
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').
|
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 |
fi
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).
|
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 |
fi
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.
|
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 |
fi
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).
|
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 |
fi
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 ‘*’).
|
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 |
fi
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Origin’ cannot be added).
|
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 |
fi
HTTP Referrer header: Length is over “%1$S” bytes limit - stripping referrer header down to origin: “%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 |
fi
HTTP Referrer header: Length of origin within referrer is over “%1$S” bytes limit - removing referrer with origin “%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 |
fi
Reporting Header: ignoring duplicated group named “%S”.
|
en-US
Reporting Header: ignoring duplicated group named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidEndpoint |
fi
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
en-US
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidItem |
fi
Reporting Header: ignoring invalid item named “%S”.
|
en-US
Reporting Header: ignoring invalid item named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidJSON |
fi
Reporting Header: invalid JSON value received.
|
en-US
Reporting Header: invalid JSON value received.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidNameItem |
fi
Reporting Header: invalid name for group.
|
en-US
Reporting Header: invalid name for group.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidURLEndpoint |
fi
Reporting Header: ignoring invalid endpoint URL “%1$S” for item named “%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 |
fi
Clear-Site-Data header forced the clean up of “%S” data.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
fi
Strict-Transport-Security: The site specified a header that could not be parsed successfully.
|
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 |
fi
Strict-Transport-Security: The site specified a header that included an invalid 'includeSubDomains' directive.
|
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 |
fi
Strict-Transport-Security: The site specified a header that included an invalid 'max-age' directive.
|
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 |
fi
Strict-Transport-Security: The site specified a header that included multiple 'includeSubDomains' directives.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
fi
Strict-Transport-Security: The site specified a header that included multiple 'max-age' directives.
|
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 |
fi
Strict-Transport-Security: The site specified a header that did not include a 'max-age' directive.
|
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 |
fi
Strict-Transport-Security: An unknown error occurred processing the header specified by the site.
|
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 |
fi
Clear-Site-Data header found. Unknown value “%S”.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties XCTOHeaderValueMissing |
fi
X-Content-Type-Options header warning: value was “%1$S”; did you mean to send “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 |
fi
Invalid X-Frame-Options header was found when loading “%2$S”: “%1$S” is not a valid directive.
|
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 | fi | en-US |
---|---|---|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
fi
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheader |
fi
sarakeotsikko
|
en-US
column header
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties header |
fi
yläotsake
|
en-US
header
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheader |
fi
riviotsikko
|
en-US
row header
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
fi
Attempt to set a forbidden header was denied: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadCryptoKeyHeader |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
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 |
fi
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.
|
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 |
fi
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.
|
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 |
fi
Warning: Source string is missing
|
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 |
fi
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').
|
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 |
fi
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').
|
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 |
fi
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').
|
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 |
fi
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').
|
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 |
fi
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').
|
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 |
fi
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).
|
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 |
fi
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.
|
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 |
fi
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).
|
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 |
fi
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 ‘*’).
|
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 |
fi
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Origin’ cannot be added).
|
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 |
fi
HTTP Referrer header: Length is over “%1$S” bytes limit - stripping referrer header down to origin: “%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 |
fi
HTTP Referrer header: Length of origin within referrer is over “%1$S” bytes limit - removing referrer with origin “%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 |
fi
Reporting Header: ignoring duplicated group named “%S”.
|
en-US
Reporting Header: ignoring duplicated group named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidEndpoint |
fi
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
en-US
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidItem |
fi
Reporting Header: ignoring invalid item named “%S”.
|
en-US
Reporting Header: ignoring invalid item named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidJSON |
fi
Reporting Header: invalid JSON value received.
|
en-US
Reporting Header: invalid JSON value received.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidNameItem |
fi
Reporting Header: invalid name for group.
|
en-US
Reporting Header: invalid name for group.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidURLEndpoint |
fi
Reporting Header: ignoring invalid endpoint URL “%1$S” for item named “%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 |
fi
Clear-Site-Data header forced the clean up of “%S” data.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
fi
Strict-Transport-Security: The site specified a header that could not be parsed successfully.
|
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 |
fi
Strict-Transport-Security: The site specified a header that included an invalid 'includeSubDomains' directive.
|
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 |
fi
Strict-Transport-Security: The site specified a header that included an invalid 'max-age' directive.
|
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 |
fi
Strict-Transport-Security: The site specified a header that included multiple 'includeSubDomains' directives.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
fi
Strict-Transport-Security: The site specified a header that included multiple 'max-age' directives.
|
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 |
fi
Strict-Transport-Security: The site specified a header that did not include a 'max-age' directive.
|
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 |
fi
Strict-Transport-Security: An unknown error occurred processing the header specified by the site.
|
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 |
fi
Clear-Site-Data header found. Unknown value “%S”.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties XCTOHeaderValueMissing |
fi
X-Content-Type-Options header warning: value was “%1$S”; did you mean to send “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 |
fi
Invalid X-Frame-Options header was found when loading “%2$S”: “%1$S” is not a valid directive.
|
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 |
fi
Resurssi osoitteessa ”%1$S” estettiin sen Cross-Origin-Resource-Policy-otsakkeen sisällön tai kyseisen otsakkeen puutteen vuoksi. Katso lisätietoja %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 |
fi
Kirjoita oma ylä-/alaotsaketekstisi
|
en-US
Please enter your custom header/footer text
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties headerFooter |
fi
Ylä- ja alaotsakkeet
|
en-US
Header and Footer
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl advanced-tab.label |
fi
Marginaalit ja ylä-/alatunnisteet
|
en-US
Margins & Header/Footer
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl custom-prompt-prompt |
fi
Kirjoita oma ylä-/alatunniste
|
en-US
Enter your custom header/footer text
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-center-tip.tooltiptext |
fi
Keskimmäinen ylätunniste
|
en-US
Center header
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-left-tip.tooltiptext |
fi
Vasen ylätunniste
|
en-US
Left header
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-right-tip.tooltiptext |
fi
Oikea ylätunniste
|
en-US
Right header
|
APIThese results are also available as an API request to search in
fi or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.