BETA

Transvision

Displaying 46 results for the string header in et:

Entity et en-US
Entity # all locales browser • browser • preferences • siteDataSettings.ftl
site-data-removing-dialog.title
et
{ site-data-removing-header }
en-US
{ site-data-removing-header }
Entity # all locales dom • chrome • accessibility • AccessFu.properties
columnheaderAbbr
et
column header
en-US
column header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
headerAbbr
et
header
en-US
header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
rowheaderAbbr
et
row header
en-US
row header
Entity # all locales dom • chrome • dom • dom.properties
ForbiddenHeaderWarning
et
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
LargeAllocationNonE10S
et
A Large-Allocation header was ignored due to the document not being loaded out of process.
en-US
A Large-Allocation header was ignored due to the document not being loaded out of process.
Entity # all locales dom • chrome • dom • dom.properties
LargeAllocationNonGetRequest
et
A Large-Allocation header was ignored due to the load being triggered by a non-GET request.
en-US
A Large-Allocation header was ignored due to the load being triggered by a non-GET request.
Entity # all locales dom • chrome • dom • dom.properties
LargeAllocationNonWin32
et
This page would be loaded in a new process due to a Large-Allocation header, however Large-Allocation process creation is disabled on non-Win32 platforms.
en-US
This page would be loaded in a new process due to a Large-Allocation header, however Large-Allocation process creation is disabled on non-Win32 platforms.
Entity # all locales dom • chrome • dom • dom.properties
LargeAllocationNotOnlyToplevelInTabGroup
et
A Large-Allocation header was ignored due to the presence of windows which have a reference to this browsing context through the frame hierarchy or window.opener.
en-US
A Large-Allocation header was ignored due to the presence of windows which have a reference to this browsing context through the frame hierarchy or window.opener.
Entity # all locales dom • chrome • dom • dom.properties
LargeAllocationSuccess
et
This page was loaded in a new process due to a Large-Allocation header.
en-US
This page was loaded in a new process due to a Large-Allocation header.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadCryptoKeyHeader
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
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 • security • security.properties
CORSAllowOriginNotMatchingOrigin
et
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
et
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
et
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
et
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
et
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
CORSMissingAllowOrigin
et
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
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).
Entity # all locales dom • chrome • security • security.properties
CORSMultipleAllowOriginNotAllowed
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
Reporting Header: invalid JSON value received.
en-US
Reporting Header: invalid JSON value received.
Entity # all locales dom • chrome • security • security.properties
ReportingHeaderInvalidNameItem
et
Reporting Header: invalid name for group.
en-US
Reporting Header: invalid name for group.
Entity # all locales dom • chrome • security • security.properties
ReportingHeaderInvalidURLEndpoint
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
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
STSUntrustworthyConnection
et
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
en-US
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
Entity # all locales dom • chrome • security • security.properties
UnknownClearSiteDataValue
et
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
et
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”?

Displaying 82 results for the string header in en-US:

Entity et en-US
Entity # all locales browser • browser • preferences • siteDataSettings.ftl
site-data-removing-dialog.title
et
{ site-data-removing-header }
en-US
{ site-data-removing-header }
Entity # all locales dom • chrome • accessibility • AccessFu.properties
columnheader
et
veeru päis
en-US
column header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
columnheaderAbbr
et
column header
en-US
column header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
header
et
päis
en-US
header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
headerAbbr
et
header
en-US
header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
rowheader
et
rea päis
en-US
row header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
rowheaderAbbr
et
row header
en-US
row header
Entity # all locales dom • chrome • dom • dom.properties
ForbiddenHeaderWarning
et
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
LargeAllocationNonE10S
et
A Large-Allocation header was ignored due to the document not being loaded out of process.
en-US
A Large-Allocation header was ignored due to the document not being loaded out of process.
Entity # all locales dom • chrome • dom • dom.properties
LargeAllocationNonGetRequest
et
A Large-Allocation header was ignored due to the load being triggered by a non-GET request.
en-US
A Large-Allocation header was ignored due to the load being triggered by a non-GET request.
Entity # all locales dom • chrome • dom • dom.properties
LargeAllocationNonWin32
et
This page would be loaded in a new process due to a Large-Allocation header, however Large-Allocation process creation is disabled on non-Win32 platforms.
en-US
This page would be loaded in a new process due to a Large-Allocation header, however Large-Allocation process creation is disabled on non-Win32 platforms.
Entity # all locales dom • chrome • dom • dom.properties
LargeAllocationNotOnlyToplevelInTabGroup
et
A Large-Allocation header was ignored due to the presence of windows which have a reference to this browsing context through the frame hierarchy or window.opener.
en-US
A Large-Allocation header was ignored due to the presence of windows which have a reference to this browsing context through the frame hierarchy or window.opener.
Entity # all locales dom • chrome • dom • dom.properties
LargeAllocationSuccess
et
This page was loaded in a new process due to a Large-Allocation header.
en-US
This page was loaded in a new process due to a Large-Allocation header.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadCryptoKeyHeader
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
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 • security • security.properties
CORSAllowOriginNotMatchingOrigin
et
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
et
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
et
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
et
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
et
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
et
Warning: Source string is missing
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
CORSMissingAllowOrigin
et
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
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).
Entity # all locales dom • chrome • security • security.properties
CORSMultipleAllowOriginNotAllowed
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
Reporting Header: invalid JSON value received.
en-US
Reporting Header: invalid JSON value received.
Entity # all locales dom • chrome • security • security.properties
ReportingHeaderInvalidNameItem
et
Reporting Header: invalid name for group.
en-US
Reporting Header: invalid name for group.
Entity # all locales dom • chrome • security • security.properties
ReportingHeaderInvalidURLEndpoint
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
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
et
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
STSUntrustworthyConnection
et
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
en-US
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
Entity # all locales dom • chrome • security • security.properties
UnknownClearSiteDataValue
et
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
et
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
et
Warning: Source string is missing
en-US
Invalid X-Frame-Options header was found when loading “%2$S”: “%1$S” is not a valid directive.
Entity # all locales editor • ui • chrome • dialogs • EditorTableProperties.dtd
cellHeader.label
et
Päis
en-US
Header
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.header.help
et
Warning: Source string is missing
en-US
Toggles visibility of the header bar.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.header.label
et
Warning: Source string is missing
en-US
Header
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.sync-header.help
et
Warning: Source string is missing
en-US
Synchronizes all views with their current header display setting.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.toggle-ui.help
et
Warning: Source string is missing
en-US
Toggles the visibility of various pieces of the user interface. <thing> must be one of: tabstrip, userlist, header, status.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.displayHeader.help
et
Warning: Source string is missing
en-US
Display the chat header on this view. This contains information like the URL of the current view, and the topic and modes for a channel view.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.displayHeader.label
et
Warning: Source string is missing
en-US
Show header
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.outputWindowURL.help
et
Warning: Source string is missing
en-US
You probably don't want to change this. The chat view loads this URL to display the actual messages, header, etc., and the file must correctly define certain items or you'll get JavaScript errors and a blank chat window!
Entity # all locales mail • chrome • messenger • CustomHeaders.dtd
newMsgHeader.label
et
Uus kirja päis:
en-US
New message header:
Entity # all locales mail • chrome • messenger • addressbook • abCard.dtd
preferDisplayName.label
et
Kuvatavat nime eelistatakse kirja päistes olevale
en-US
Always prefer display name over message header
Entity # all locales mail • chrome • messenger • custom.properties
colonInHeaderName
et
Päis, mille sisestasid, sisaldab keelatud tähemärki, nagu näiteks koolon, esituseta tähemärk või mitte-ascii tähemärk. Palun kustuta keelatud tähemärk ning proovi uuesti.
en-US
The header you entered contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight bit ascii character. Please remove the invalid character and try again.
Entity # all locales mail • chrome • messenger • filter.properties
invalidCustomHeader
et
Üks sinu filter kasutab kohandatud päist, mis sisaldab keelatud märki nagu ':', mitteprinditavat märki, ASCII-välist märki või kaheksabitist ASCII märki. Palun redigeeri faili msgFilterRules.dat, mis sisaldab sinu filtreid, ja eemalda kohandatud päistest keelatud märgid.
en-US
One of your filters uses a custom header that contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers.
Entity # all locales mail • chrome • messenger • imapMsgs.properties
imapReceivingMessageHeaders3
et
Kirjade päiste tõmbamine kausta %3$S: %1$S/%2$S
en-US
Downloading message header %1$S of %2$S in %3$S
Entity # all locales mail • chrome • messenger • messengercompose • EditorTableProperties.dtd
cellHeader.label
et
Päis
en-US
Header
Entity # all locales mail • messenger • openpgp • msgReadStatus.ftl
message-security-button.title
et
Warning: Source string is missing
en-US
{ PLATFORM() -> [macos] Show Message Security (⌃ ⌘ { message-header-show-security-info-key }) *[other] Show Message Security (Ctrl+Alt+{ message-header-show-security-info-key }) }
Entity # all locales mail • messenger • preferences • preferences.ftl
chat-header-label.label
et
Kuva päist
en-US
Show Header
Entity # all locales suite • chrome • editor • dialogs • EditorTableProperties.dtd
cellHeader.label
et
Warning: Source string is missing
en-US
Header
Entity # all locales suite • chrome • mailnews • CustomHeaders.dtd
newMsgHeader.label
et
Warning: Source string is missing
en-US
New message header:
Entity # all locales suite • chrome • mailnews • addressbook • abCardOverlay.dtd
preferDisplayName.label
et
Warning: Source string is missing
en-US
Always prefer display name over message header
Entity # all locales suite • chrome • mailnews • custom.properties
colonInHeaderName
et
Warning: Source string is missing
en-US
The header you entered contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight bit ascii character. Please remove the invalid character and try again.
Entity # all locales suite • chrome • mailnews • filter.properties
invalidCustomHeader
et
Warning: Source string is missing
en-US
One of your filters uses a custom header that contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers.
Entity # all locales suite • chrome • mailnews • imapMsgs.properties
imapReceivingMessageHeaders3
et
Warning: Source string is missing
en-US
Downloading message header %1$S of %2$S in %3$S
Entity # all locales suite • chrome • mailnews • pref • pref-composing_messages.dtd
noReplyOption.label
et
Warning: Source string is missing
en-US
No Reply Header
Entity # all locales suite • chrome • mailnews • pref • pref-composing_messages.dtd
selectHeaderType.label
et
Warning: Source string is missing
en-US
Select reply header type:
Entity # all locales toolkit • chrome • global • printdialog.properties
customHeaderFooterPrompt
et
Palun sisesta oma kohandatud päise/jaluse tekst
en-US
Please enter your custom header/footer text
Entity # all locales toolkit • chrome • global • printdialog.properties
headerFooter
et
Päis ja jalus
en-US
Header and Footer
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
advanced-tab.label
et
Veerised ja päis/jalus
en-US
Margins & Header/Footer
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
custom-prompt-prompt
et
Sisesta päise/jaluse tekst
en-US
Enter your custom header/footer text
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
header-center-tip.tooltiptext
et
Keskmine päis
en-US
Center header
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
header-left-tip.tooltiptext
et
Vasak päis
en-US
Left header
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
header-right-tip.tooltiptext
et
Parem päis
en-US
Right header
Please enable JavaScript. Some features won't be available without it.