BETA

Transvision

Displaying 47 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
LargeAllocationNonE10S
fi
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
fi
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
fi
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
fi
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
fi
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
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 • 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
CORSMissingAllowOrigin
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).
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
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
STSUntrustworthyConnection
fi
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
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 extensions • irc • chrome • chatzilla.properties
cmd.toggle-ui.help
fi
Vaihtaa käyttöliittymän osien näkyvyyttä. <Thingin> tulee olla jokin seuraavista: tabstrip (lista avoimista näkymistä), userlist (käyttäjälista), header (otsakepalkki) tai status (tilarivi).
en-US
Toggles the visibility of various pieces of the user interface. <thing> must be one of: tabstrip, userlist, header, status.
Entity # all locales mail • messenger • openpgp • msgReadStatus.ftl
message-security-button.title
fi
{ PLATFORM() -> [macos] Näytä viestin tietosuoja (⌘ ⌥ { message-header-show-security-info-key }) *[other] Näytä viestin tietosuoja (Ctrl+Alt+{ message-header-show-security-info-key }) }
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 }) }

Displaying 82 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
columnheaderAbbr
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
headerAbbr
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 • accessibility • AccessFu.properties
rowheaderAbbr
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
LargeAllocationNonE10S
fi
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
fi
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
fi
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
fi
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
fi
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
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 • 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
CORSMissingAllowOrigin
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).
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
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
STSUntrustworthyConnection
fi
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
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 editor • ui • chrome • dialogs • EditorTableProperties.dtd
cellHeader.label
fi
Otsikko
en-US
Header
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.header.help
fi
Näyttää tai piilottaa otsakepalkin.
en-US
Toggles visibility of the header bar.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.header.label
fi
Otsakepalkki
en-US
Header
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.sync-header.help
fi
Synkronoi kaikki näkymät nykyisten välitystietojen näyttöasetustensa kanssa.
en-US
Synchronizes all views with their current header display setting.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.toggle-ui.help
fi
Vaihtaa käyttöliittymän osien näkyvyyttä. <Thingin> tulee olla jokin seuraavista: tabstrip (lista avoimista näkymistä), userlist (käyttäjälista), header (otsakepalkki) tai status (tilarivi).
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
fi
Näyttää keskusteluotsikon tässä näkymässä. Keskusteluotsikossa lukee mm. nykyisen näkymän osoite sekä kanavanäkymän aihe ja tilat.
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
fi
Näytä otsikko
en-US
Show header
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.outputWindowURL.help
fi
Sinun ei todennäköisesti tarvitse muuttaa tätä. Tämä osoite ladataan keskustelunäkymään todellisten viestien, otsikon ym. näyttämiseksi, ja tiedoston täytyy määrittää tiettyjä merkintöjä oikein, tai muuten näet vain JavaScript-virheitä ja tyhjän keskusteluikkunan!
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
fi
Uusi otsaketieto:
en-US
New message header:
Entity # all locales mail • chrome • messenger • addressbook • abCard.dtd
preferDisplayName.label
fi
Käytä aina mieluummin näyttönimeä kuin viestin aihetta
en-US
Always prefer display name over message header
Entity # all locales mail • chrome • messenger • custom.properties
colonInHeaderName
fi
Antamasi otsake sisältää virheellisiä merkkejä, kuten ":", ei-tulostettavan merkin, ascii-merkistöön kuulumattoman merkin tai kahdeksanbittisen ascii-merkin. Poista virheellinen merkki ja yritä uudelleen.
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
fi
Yksi suodattimistasi käyttää otsaketta, jossa on virheellinen merkki, kuten ":", ei-tulostuva merkki, muu kuin ascii-merkki tai 8-bittinen ascii-merkki. Muokkaa msgFilterRules.dat -tiedostoa, joka sisältää suodattimesi, poistaaksesi virheelliset merkit otsakkeista.
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
fi
Ladataan viestiotsikkoa %1$S/%2$S kansioon %3$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
fi
Otsikko
en-US
Header
Entity # all locales mail • messenger • openpgp • msgReadStatus.ftl
message-security-button.title
fi
{ PLATFORM() -> [macos] Näytä viestin tietosuoja (⌘ ⌥ { message-header-show-security-info-key }) *[other] Näytä viestin tietosuoja (Ctrl+Alt+{ message-header-show-security-info-key }) }
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
fi
Näytä otsikko
en-US
Show Header
Entity # all locales suite • chrome • editor • dialogs • EditorTableProperties.dtd
cellHeader.label
fi
Otsikko
en-US
Header
Entity # all locales suite • chrome • mailnews • CustomHeaders.dtd
newMsgHeader.label
fi
Uusi välitystieto:
en-US
New message header:
Entity # all locales suite • chrome • mailnews • addressbook • abCardOverlay.dtd
preferDisplayName.label
fi
Käytä aina kokonimeä viestiotsikossa olevan sijaan
en-US
Always prefer display name over message header
Entity # all locales suite • chrome • mailnews • custom.properties
colonInHeaderName
fi
Annettu välitystieto sisältää jonkun kielletyistä merkeistä, esim. kaksoispiste, tulostumaton merkki, merkki joka ei ole ASCII-merkki, tai 8-bittinen ASCII-merkki. Poista kielletty merkki ja yritä uudelleen.
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
fi
Yksi suodattimistasi käyttää otsaketta, jossa on virheellinen merkki, kuten :, ei-tulostuva merkki, muu kuin ascii-merkki tai 8-bittinen ascii-merkki. Poista virheelliset merkit otsakkeista muokkaamalla tiedostoa msgFilterRules.dat, joka sisältää suodattimesi.
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
fi
Ladataan viestiotsikkoa %1$S/%2$S kansioon %3$S
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
fi
Ei vastausotsaketta
en-US
No Reply Header
Entity # all locales suite • chrome • mailnews • pref • pref-composing_messages.dtd
selectHeaderType.label
fi
Valitse vastausotsakkeen tyyppi:
en-US
Select reply header type:
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
Please enable JavaScript. Some features won't be available without it.