Main Views
QA Views
About Transvision
BETA
Displaying 38 results for the string header in fy-NL:
| Entity | fy-NL | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
fy-NL
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
fy-NL
Besykjen om in ferbeane header yn te stellen waard wegere: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonE10S |
fy-NL
In Large-Allocation-header is negearre, omdat it dokumint net út it proses laden wurdt.
|
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 |
fy-NL
In Large-Allocation-header is negearre troch in non-GET-fersyk oproppen belesting.
|
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 |
fy-NL
As gefolch fan in Large-Allocation-header soe dizze side laden wurde yn in nij proses, mar it meitsjen fan in Large-Allocation-proses is útskeakele op net-Win-32-platfoarms.
|
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 |
fy-NL
In Large-Allocation-header is negearre troch de oanwêzichheid fan finsters dy't in referinsje hawwe nei dizze browserkontekst troch de framehierargy of 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 |
fy-NL
Dizze side is laden yn in nij proses troch in Larde-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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De header ‘Kryptokaai’ moat in parameter ‘dh’ befetsje mei de publike kaai fan de appserver. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De header ‘Ynhâldsfersifering’ moat ‘aesgcm’ wêze. ‘aescgm128’ is tastien, mar net langer stipe en sil ynkoarten fuortsmiten wurde. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De header ‘Fersifering’ moat in unike parameter ‘salt’ befetsje foar elk berjocht. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De header ‘Fersiferingskaai’ moat in parameter ‘dh’ befetsje. Dizze header wurdt net langer stipe en sil ynkoarten fuortsmiten wurde. Brûk yn stee derfan ‘Kryptokaai’ mei ‘Content-Encoding: aesgcm‘. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De parameter ‘rs’ yn de header ‘Encryption’ moat lizze tusken %2$S en 2^36-31, of folslein fuort litten wurde. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De parameter ‘salt’ yn de header ‘Encryption’ moat fersifere wêze mei base-64-url (https://tools.ietf.org/html/rfc7515#appendix-C) en op syn minst 16 bytes yn-it-foar fersifering). Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De parameter ‘dh’ yn de header ‘Crypto-Key’ moat publike Diffie-Hellman-kaai fan de app-server wêze, fersifere mei base-64-url (https://tools.ietf.org/html/rfc7515#appendix-C) en yn de foarm ‘net-komprimearre’ of ‘raw’ (65 bytes yn-it-foar fersifering). Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4.
|
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 |
fy-NL
Registrearjen fan in ServiceWorker is mislearre: it paad fan it opjûne berik ‘%1$S’ stiet net ûnder it maksimaal tastiene berik ‘%2$S’. Pas it berik oan, ferpleats it ServiceWorker-script, of brûk de Service-Worker-Allowed HTTP-header om it berik ta te stean.
|
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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: CORS-header 'Access-Control-Allow-Origin' komt net oerien mei '%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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: ûnjildich token '%2$S' yn 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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: ûnjildich token '%2$S' yn 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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: de metoade yn CORS-header 'Access-Control-Allow-Methods' waard net fûn).
|
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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: 'true' ferwacht yn 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 |
fy-NL
Cross-Origin-oanfraach blokkearre: de Same Origin Policy stiet it lêzen fan de eksterne boarne op %1$S net ta. (Reden: header ‘%2$S’ is neffens header ‘Access-Control-Allow-Headers’ fan it CORS-preflight-antwurd net tastien).
|
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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: CORS-header 'Access-Control-Allow-Origin' mist).
|
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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: Multy-CORS-header 'Access-Control-Allow-Origin' net tastien).
|
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 |
fy-NL
Fersyk foar cross-origin blokkearre: itselde origin-belied stiet it lêzen fan de eksterne boarne op ‘%1$S’ net ta. (Reden: referinsjes wurde net stipe as de 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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: CORS-header ‘Origin’ kin net tafoege wurde).
|
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 |
fy-NL
HTTP Referrer header: De lingte is grutter as de limyt fan ‘%1$S’ bytes – referrer header wurdt werombrocht nei iet orizjineel: ‘%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 |
fy-NL
HTTP Referrer header: De lingte fan it orizjineel yn de referrer is grutter as de limyt fan ‘%1$S’ bytes – referrer mei oarsprong ‘%2$S’ wurdt fuortsmiten.
|
en-US
HTTP Referrer header: Length of origin within referrer is over “%1$S” bytes limit - removing referrer with origin “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties RunningClearSiteDataValue |
fy-NL
Clear-Site-Data-header hat it opskjinjen fan gegevens fan ‘%S’ ôftwongen.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't net mei sukses parset wurde koe.
|
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 |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't in ûnjildige ‘includeSubDomains’-ynstruksje befette.
|
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 |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't in ûnjildige ‘max-age’-ynstruksje befette.
|
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 |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't mear ‘includeSubDomains’-ynstruksjes befette.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't mear ‘max-age’-ynstruksjes befette.
|
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 |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't gjin ‘max-age’-ynstruksje befette.
|
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 |
fy-NL
Strict-Transport-Security: der is in ûnbekende flater bard by it ferwurkjen fan de troch de website spesifisearre header.
|
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 |
fy-NL
Strict-Transport-Security: de ferbining mei de website is net betrouber, dus de spesifisearre header waard negearre.
|
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 |
fy-NL
Clear-Site-Data-header fûn. Unbekende wearde ‘%S’.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl message-security-button.title |
fy-NL
{ PLATFORM() ->
[macos] Berjochtbefeiliging toane (⌘ ⌥ { message-header-show-security-info-key })
*[other] Berjochtbefeiliging toane (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 | fy-NL | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
fy-NL
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheader |
fy-NL
kolomtitel
|
en-US
column header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheaderAbbr |
fy-NL
kolomtitel
|
en-US
column header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties header |
fy-NL
koptekst
|
en-US
header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties headerAbbr |
fy-NL
koptekst
|
en-US
header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheader |
fy-NL
rigekoptekst
|
en-US
row header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheaderAbbr |
fy-NL
rigekoptekst
|
en-US
row header
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
fy-NL
Besykjen om in ferbeane header yn te stellen waard wegere: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonE10S |
fy-NL
In Large-Allocation-header is negearre, omdat it dokumint net út it proses laden wurdt.
|
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 |
fy-NL
In Large-Allocation-header is negearre troch in non-GET-fersyk oproppen belesting.
|
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 |
fy-NL
As gefolch fan in Large-Allocation-header soe dizze side laden wurde yn in nij proses, mar it meitsjen fan in Large-Allocation-proses is útskeakele op net-Win-32-platfoarms.
|
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 |
fy-NL
In Large-Allocation-header is negearre troch de oanwêzichheid fan finsters dy't in referinsje hawwe nei dizze browserkontekst troch de framehierargy of 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 |
fy-NL
Dizze side is laden yn in nij proses troch in Larde-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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De header ‘Kryptokaai’ moat in parameter ‘dh’ befetsje mei de publike kaai fan de appserver. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De header ‘Ynhâldsfersifering’ moat ‘aesgcm’ wêze. ‘aescgm128’ is tastien, mar net langer stipe en sil ynkoarten fuortsmiten wurde. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De header ‘Fersifering’ moat in unike parameter ‘salt’ befetsje foar elk berjocht. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De header ‘Fersiferingskaai’ moat in parameter ‘dh’ befetsje. Dizze header wurdt net langer stipe en sil ynkoarten fuortsmiten wurde. Brûk yn stee derfan ‘Kryptokaai’ mei ‘Content-Encoding: aesgcm‘. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De parameter ‘rs’ yn de header ‘Encryption’ moat lizze tusken %2$S en 2^36-31, of folslein fuort litten wurde. Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De parameter ‘salt’ yn de header ‘Encryption’ moat fersifere wêze mei base-64-url (https://tools.ietf.org/html/rfc7515#appendix-C) en op syn minst 16 bytes yn-it-foar fersifering). Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1.
|
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 |
fy-NL
It is de ServiceWorker foar scope ‘%1$S’ net slagge in push-berjocht te ûntsiferjen. De parameter ‘dh’ yn de header ‘Crypto-Key’ moat publike Diffie-Hellman-kaai fan de app-server wêze, fersifere mei base-64-url (https://tools.ietf.org/html/rfc7515#appendix-C) en yn de foarm ‘net-komprimearre’ of ‘raw’ (65 bytes yn-it-foar fersifering). Mear ynfo op https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4.
|
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 |
fy-NL
Registrearjen fan in ServiceWorker is mislearre: it paad fan it opjûne berik ‘%1$S’ stiet net ûnder it maksimaal tastiene berik ‘%2$S’. Pas it berik oan, ferpleats it ServiceWorker-script, of brûk de Service-Worker-Allowed HTTP-header om it berik ta te stean.
|
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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: CORS-header 'Access-Control-Allow-Origin' komt net oerien mei '%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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: ûnjildich token '%2$S' yn 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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: ûnjildich token '%2$S' yn 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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: de metoade yn CORS-header 'Access-Control-Allow-Methods' waard net fûn).
|
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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: 'true' ferwacht yn 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 |
fy-NL
Cross-Origin-oanfraach blokkearre: de Same Origin Policy stiet it lêzen fan de eksterne boarne op %1$S net ta. (Reden: header ‘%2$S’ is neffens header ‘Access-Control-Allow-Headers’ fan it CORS-preflight-antwurd net tastien).
|
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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: CORS-header 'Access-Control-Allow-Origin' mist).
|
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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: Multy-CORS-header 'Access-Control-Allow-Origin' net tastien).
|
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 |
fy-NL
Fersyk foar cross-origin blokkearre: itselde origin-belied stiet it lêzen fan de eksterne boarne op ‘%1$S’ net ta. (Reden: referinsjes wurde net stipe as de 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 |
fy-NL
Cross-origin-fersyk blokkearre: Itselde orizjinele belied stiet it lêzen fan de oare boarne op %1$S net ta. (Reden: CORS-header ‘Origin’ kin net tafoege wurde).
|
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 |
fy-NL
HTTP Referrer header: De lingte is grutter as de limyt fan ‘%1$S’ bytes – referrer header wurdt werombrocht nei iet orizjineel: ‘%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 |
fy-NL
HTTP Referrer header: De lingte fan it orizjineel yn de referrer is grutter as de limyt fan ‘%1$S’ bytes – referrer mei oarsprong ‘%2$S’ wurdt fuortsmiten.
|
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 |
fy-NL
Rapportaazjeheader: duplisearre groep mei namme ‘%S’ negearre.
|
en-US
Reporting Header: ignoring duplicated group named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidEndpoint |
fy-NL
Rapportaazjeheader: net jildich einpunt foar item mei namme ‘%S’ negearre.
|
en-US
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidItem |
fy-NL
Rapportaazjeheader: net jildich item mei namme ‘%S’ negearre.
|
en-US
Reporting Header: ignoring invalid item named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidJSON |
fy-NL
Rapportaazjeheader: net jildige JSON-wearde ûntfongen.
|
en-US
Reporting Header: invalid JSON value received.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidNameItem |
fy-NL
Rapportaazjeheader: net jildige namme foar groep.
|
en-US
Reporting Header: invalid name for group.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidURLEndpoint |
fy-NL
Rapportaazjeheader: net jildige einpunt-URL ‘%1$S’ foar item mei namme ‘%2$S’ negearre.
|
en-US
Reporting Header: ignoring invalid endpoint URL “%1$S” for item named “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties RunningClearSiteDataValue |
fy-NL
Clear-Site-Data-header hat it opskjinjen fan gegevens fan ‘%S’ ôftwongen.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't net mei sukses parset wurde koe.
|
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 |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't in ûnjildige ‘includeSubDomains’-ynstruksje befette.
|
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 |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't in ûnjildige ‘max-age’-ynstruksje befette.
|
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 |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't mear ‘includeSubDomains’-ynstruksjes befette.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't mear ‘max-age’-ynstruksjes befette.
|
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 |
fy-NL
Strict-Transport-Security: de website hat in header spesifisearre dy't gjin ‘max-age’-ynstruksje befette.
|
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 |
fy-NL
Strict-Transport-Security: der is in ûnbekende flater bard by it ferwurkjen fan de troch de website spesifisearre header.
|
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 |
fy-NL
Strict-Transport-Security: de ferbining mei de website is net betrouber, dus de spesifisearre header waard negearre.
|
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 |
fy-NL
Clear-Site-Data-header fûn. Unbekende wearde ‘%S’.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties XCTOHeaderValueMissing |
fy-NL
X-Content-Type-Options-headerwarskôging: wearde wie ‘%1$S’; woene jo ‘nosniff’ ferstjoere?
|
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 |
fy-NL
Der is in ûnjildige X-Frame-Options-koptekst fûn by it laden fan ‘%2$S’: ‘%1$S’ is gjin jildige rjochtline.
|
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 |
fy-NL
Kop
|
en-US
Header
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.header.help |
fy-NL
Warning: Source string is missing
|
en-US
Toggles visibility of the header bar.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.header.label |
fy-NL
Warning: Source string is missing
|
en-US
Header
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.sync-header.help |
fy-NL
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 |
fy-NL
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 |
fy-NL
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 |
fy-NL
Warning: Source string is missing
|
en-US
Show header
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties pref.outputWindowURL.help |
fy-NL
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 |
fy-NL
Nije koprigel:
|
en-US
New message header:
|
|
Entity
#
all locales
mail • chrome • messenger • addressbook • abCard.dtd preferDisplayName.label |
fy-NL
Altyd werjeftenamme boppe berjochtkop toane
|
en-US
Always prefer display name over message header
|
|
Entity
#
all locales
mail • chrome • messenger • custom.properties colonInHeaderName |
fy-NL
De koprigel dy't jo ynfierd hawwe befettet in ûnjildich teken, lykas ':', in net-ôfdrukber teken, in net-ascii-teken, of in 8-bits ascii-teken. Smyt it ûnjildige teken fuort en probearje it opnij.
|
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 |
fy-NL
Ien fan jo filters brûkt in oanpaste koprigel dy't in ûnjildich teken befettet, lykas ‘:’, in net ôf te drukken teken, in net-ascii-teken, of in 8-bits ascii-teken. Bewurkje it bestân msgFilterRules.dat, dêr't jo filters yn steane, om ûnjildige tekens út jo oanpaste koprigels fuort te smiten.
|
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 |
fy-NL
berjochtkop %1$S fan %2$S nei %3$S downloade…
|
en-US
Downloading message header %1$S of %2$S in %3$S…
|
|
Entity
#
all locales
mail • chrome • messenger • messengercompose • EditorTableProperties.dtd cellHeader.label |
fy-NL
Kop
|
en-US
Header
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl message-security-button.title |
fy-NL
{ PLATFORM() ->
[macos] Berjochtbefeiliging toane (⌘ ⌥ { message-header-show-security-info-key })
*[other] Berjochtbefeiliging toane (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 |
fy-NL
Kop toane
|
en-US
Show Header
|
|
Entity
#
all locales
suite • chrome • editor • dialogs • EditorTableProperties.dtd cellHeader.label |
fy-NL
Warning: Source string is missing
|
en-US
Header
|
|
Entity
#
all locales
suite • chrome • mailnews • CustomHeaders.dtd newMsgHeader.label |
fy-NL
Warning: Source string is missing
|
en-US
New message header:
|
|
Entity
#
all locales
suite • chrome • mailnews • addressbook • abCardOverlay.dtd preferDisplayName.label |
fy-NL
Warning: Source string is missing
|
en-US
Always prefer display name over message header
|
|
Entity
#
all locales
suite • chrome • mailnews • custom.properties colonInHeaderName |
fy-NL
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 |
fy-NL
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 |
fy-NL
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 |
fy-NL
Warning: Source string is missing
|
en-US
No Reply Header
|
|
Entity
#
all locales
suite • chrome • mailnews • pref • pref-composing_messages.dtd selectHeaderType.label |
fy-NL
Warning: Source string is missing
|
en-US
Select reply header type:
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties customHeaderFooterPrompt |
fy-NL
Jou jo eigen kop-/fuottekst
|
en-US
Please enter your custom header/footer text
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties headerFooter |
fy-NL
Kop- en fuottekst
|
en-US
Header and Footer
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl advanced-tab.label |
fy-NL
Marzjes & kop-/fuotteksten
|
en-US
Margins & Header/Footer
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl custom-prompt-prompt |
fy-NL
Meitsje jo eigen kop-/fuottekst
|
en-US
Enter your custom header/footer text
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-center-tip.tooltiptext |
fy-NL
Middelste koptekst
|
en-US
Center header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-left-tip.tooltiptext |
fy-NL
Lofter koptekst
|
en-US
Left header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-right-tip.tooltiptext |
fy-NL
Rjochter koptekst
|
en-US
Right header
|
APIThese results are also available as an API request to search in
fy-NL or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.