Main Views
QA Views
About Transvision
BETA
Displaying 16 results for the string header in lij:
Entity | lij | en-US |
---|---|---|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
lij
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.custom.headers |
lij
Header da domanda:
|
en-US
Request Headers
|
Entity
#
all locales
dom • chrome • security • security.properties CORSAllowOriginNotMatchingOrigin |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: header CORS “Access-Control-Allow-Origin” no corrisponde a “%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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: token “%2$S” no bon in header CORS “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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: token “%2$S” no bon in header CORS “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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine no consente a letua da risorsa remòtta da %1$S. Motivo: metodo “Access-Control-Allow-Methods” no trovou in header CORS.
|
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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: m'aspetavo “true” in header CORS “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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: header CORS “Access-Control-Allow-Origin” no gh'é.
|
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 STSCouldNotParseHeader |
lij
Strict-Transport-Security: no l'é stæto poscibile analizâ ben l’header specificou da-o scito.
|
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 |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header ch'o l'includde 'na diretiva “includeSubDomains” no valida.
|
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 |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header che includde 'na diretiva “max-age” no valida.
|
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 |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header ch'o l'includde ciù diretive “includeSubDomains”.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header che includde ciù diretive “max-age”.
|
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 |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header che no includde 'na diretiva “max-age”.
|
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 |
lij
Strict-Transport-Security: gh'é stæto 'n erô inte l'analixi de l'header specificou da-o scito.
|
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 |
lij
Strict-Transport-Security: l’header specificou da-o scito o l'é stæto ignorou perché a conescion a no l'é afidabile.
|
en-US
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
|
Displaying 82 results for the string header in en-US:
Entity | lij | en-US |
---|---|---|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
lij
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheader |
lij
testâ da colònna
|
en-US
column header
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheaderAbbr |
lij
intest. colònna
|
en-US
column header
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties header |
lij
testâ
|
en-US
header
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties headerAbbr |
lij
intestaç.
|
en-US
header
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheader |
lij
testâ da riga
|
en-US
row header
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheaderAbbr |
lij
intest. riga
|
en-US
row header
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
lij
Tentativo de inpostâ 'na testâ proibio negou: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonE10S |
lij
Ina testâ Large-Allocation a l'é stæta ignorâ perché o documento o no l'é stæto caregou feua do processo.
|
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 |
lij
Ina testâ Large-Allocation a l'é stæta ignorâ perché o caregamento o l'é arivou da 'na domanda che no l'ea GET.
|
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 |
lij
Sta pagina a saiâ caregâ inte neuvo processo perché gh'é 'na testâ Large-Allocation, a ògni mòddo a creaçion de 'n processo con Large-Allocation a l'é dizabilitâ inte piataforme no Win32.
|
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 |
lij
Ina testâ Large-Allocation a l'é stæta ignorâ perché gh'ea di barcoin che gh'aivan 'n riferimento a sto contesto de navegaçion atraverso o gerarchia di frame ò 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 |
lij
Sta pagina a l'é stæta caregâ torna inte neuvo processo pe caxon da seu testâ Large-Allocation.
|
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 |
lij
O ServiceWorker pe ‘%1$S’ o no l'é ariescio a descriptâ 'n mesagio push. A testâ de ‘Crypto-Key’ a deve includde un unico parametro ‘dh‘ pe ògni mesagio. Amia https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 pe saveine de ciù.
|
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 |
lij
O ServiceWorker pe ‘%1$S’ o no l'é ariescio a descriptâ ìn mesagio push. A testâ de ‘Content-Encoding’ a dev'ese ‘aesgcm‘. ‘aesgcm128‘ o l'é permisso ma deprecou e saiâ fito scancelou. Pe piaxei deuvia ‘Crypto-Key‘ con ‘Content-Encoding: aesgcm‘ in cangio. Amia https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 pe saveine de ciù.
|
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 |
lij
O ServiceWorker pe ‘%1$S’ o no l'é ariescio a descriptâ in mesagio push. A testâ de ‘Encryption’ a deve includde un unico parametro ‘salt‘ pe ògni mesagio. Amia https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 pe saveine de ciù.
|
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 |
lij
O ServiceWorker pe ‘%1$S’ o no l'é ariescio a descriptâ ìn mesagio push. A testâ de ‘Encryption-Key’ a deve includde un parametro ‘dh‘ pe ògni mesagio. Sta testâ a l'é deprecâ e saiâ fito scancelâ. Pe piaxei deuvia ‘Crypto-Key‘ con ‘Content-Encoding: aesgcm‘ in cangio. Amia https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 pe saveine de ciù.
|
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 |
lij
O ServiceWorker pe ‘%1$S’ o no l'é ariescio a descriptâ ìn mesagio push. O parametro ‘rs‘ inta testâ ‘Encryption‘ a deve ese fra %2$S e 2^36-31, ò no deve esighe pe ninte. Amia chi https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 pe saveine de ciù.
|
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 |
lij
O ServiceWorker pe ‘%1$S’ o no l'é ariescio a descriptâ ìn mesagio push. O parametro ‘salt‘ inta testâ ‘Encryption‘ a deve ese base64utl-encoded (https://tools.ietf.org/html/rfc7515#appendix-C), e avei armeno 16 bytes primma da scritograçion. Amia chi https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 pe saveine de ciù.
|
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 |
lij
O ServiceWorker pe ‘%1$S’ o no l'é ariescio a descriptâ ìn mesagio push. O parametro ‘dh‘ inta testâ ‘Crypto-Key‘ a deve ese inta ciave pubrica Diffie-Hellman, base64utl-encoded do server de aplicaçioin (https://tools.ietf.org/html/rfc7515#appendix-C) e into formou “uncompressed” or “raw” (65 bytes primma da codifica). Amia chi https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 pe saveine de ciù.
|
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 |
lij
No son areiscio a registrâ un ServiceWorker: o percorso pe sto anbito %1$S’ o no l'é meno do mascimo scope permisso ‘%2$S’, Scistema o scope, mescia o script do Service Worker, ò deuvia 'na testâ HTTP Service-Worker-Allowed pe permette l'anbito.
|
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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: header CORS “Access-Control-Allow-Origin” no corrisponde a “%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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: token “%2$S” no bon in header CORS “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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: token “%2$S” no bon in header CORS “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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine no consente a letua da risorsa remòtta da %1$S. Motivo: metodo “Access-Control-Allow-Methods” no trovou in header CORS.
|
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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: m'aspetavo “true” in header CORS “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 |
lij
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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de corispondensa de òrigine o no consente a letua da risorsa remòtta da %1$S. Motivo: header CORS “Access-Control-Allow-Origin” no gh'é.
|
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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio de mæxima òrigine a no permette a risorsa remòtta in %1$S. (Raxon: testâ moltipla CORS ‘Access-Control-Allow-Origin’ no permissa).
|
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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: o criteio da mæxima òrigine a no permette de leze a risorsa remòtta in ‘%1$S’. (Raxon: E credensiali no en soportæ se a testâ CORS ‘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 |
lij
Domanda moltiòrigine (cross-origin) blocâ: a mæxima politica de òrigine a no permette a letua da risorsa remòtta da %1$S. (Motivo: testâ CORS ‘Origin’ a no peu ese azonta).
|
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 |
lij
Warning: Source string is missing
|
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 |
lij
Warning: Source string is missing
|
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 |
lij
Warning: Source string is missing
|
en-US
Reporting Header: ignoring duplicated group named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidEndpoint |
lij
Warning: Source string is missing
|
en-US
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidItem |
lij
Warning: Source string is missing
|
en-US
Reporting Header: ignoring invalid item named “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidJSON |
lij
Warning: Source string is missing
|
en-US
Reporting Header: invalid JSON value received.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidNameItem |
lij
Warning: Source string is missing
|
en-US
Reporting Header: invalid name for group.
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidURLEndpoint |
lij
Warning: Source string is missing
|
en-US
Reporting Header: ignoring invalid endpoint URL “%1$S” for item named “%2$S”.
|
Entity
#
all locales
dom • chrome • security • security.properties RunningClearSiteDataValue |
lij
Testâ Clear-Site-Data o l'à forsou o netezzo di dæti “%S”.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
lij
Strict-Transport-Security: no l'é stæto poscibile analizâ ben l’header specificou da-o scito.
|
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 |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header ch'o l'includde 'na diretiva “includeSubDomains” no valida.
|
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 |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header che includde 'na diretiva “max-age” no valida.
|
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 |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header ch'o l'includde ciù diretive “includeSubDomains”.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header che includde ciù diretive “max-age”.
|
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 |
lij
Strict-Transport-Security: o scito o l'à specificou 'n header che no includde 'na diretiva “max-age”.
|
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 |
lij
Strict-Transport-Security: gh'é stæto 'n erô inte l'analixi de l'header specificou da-o scito.
|
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 |
lij
Strict-Transport-Security: l’header specificou da-o scito o l'é stæto ignorou perché a conescion a no l'é afidabile.
|
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 |
lij
Atrovâ a Testâ Clear-Site-Data. Valô no conosciuo “%S”.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
Entity
#
all locales
dom • chrome • security • security.properties XCTOHeaderValueMissing |
lij
Alarme da testâ de X-Content-Type-Options: o valô o l'ea “%1$S”; t'örieivi miga mandâ “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 |
lij
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 |
lij
Warning: Source string is missing
|
en-US
Header
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.header.help |
lij
Warning: Source string is missing
|
en-US
Toggles visibility of the header bar.
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.header.label |
lij
Warning: Source string is missing
|
en-US
Header
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.sync-header.help |
lij
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 |
lij
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 |
lij
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 |
lij
Warning: Source string is missing
|
en-US
Show header
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties pref.outputWindowURL.help |
lij
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 |
lij
Warning: Source string is missing
|
en-US
New message header:
|
Entity
#
all locales
mail • chrome • messenger • addressbook • abCard.dtd preferDisplayName.label |
lij
Warning: Source string is missing
|
en-US
Always prefer display name over message header
|
Entity
#
all locales
mail • chrome • messenger • custom.properties colonInHeaderName |
lij
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
mail • chrome • messenger • filter.properties invalidCustomHeader |
lij
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
mail • chrome • messenger • imapMsgs.properties imapReceivingMessageHeaders3 |
lij
Warning: Source string is missing
|
en-US
Downloading message header %1$S of %2$S in %3$S…
|
Entity
#
all locales
mail • chrome • messenger • messengercompose • EditorTableProperties.dtd cellHeader.label |
lij
Warning: Source string is missing
|
en-US
Header
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl message-security-button.title |
lij
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 |
lij
Warning: Source string is missing
|
en-US
Show Header
|
Entity
#
all locales
suite • chrome • editor • dialogs • EditorTableProperties.dtd cellHeader.label |
lij
Warning: Source string is missing
|
en-US
Header
|
Entity
#
all locales
suite • chrome • mailnews • CustomHeaders.dtd newMsgHeader.label |
lij
Warning: Source string is missing
|
en-US
New message header:
|
Entity
#
all locales
suite • chrome • mailnews • addressbook • abCardOverlay.dtd preferDisplayName.label |
lij
Warning: Source string is missing
|
en-US
Always prefer display name over message header
|
Entity
#
all locales
suite • chrome • mailnews • custom.properties colonInHeaderName |
lij
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 |
lij
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 |
lij
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 |
lij
Warning: Source string is missing
|
en-US
No Reply Header
|
Entity
#
all locales
suite • chrome • mailnews • pref • pref-composing_messages.dtd selectHeaderType.label |
lij
Warning: Source string is missing
|
en-US
Select reply header type:
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties customHeaderFooterPrompt |
lij
Pe piaxei scrivi o testo pe-a çimma/fondo
|
en-US
Please enter your custom header/footer text
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties headerFooter |
lij
Çimma e Fondo da pagina
|
en-US
Header and Footer
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl advanced-tab.label |
lij
Margini & Çimma/Fondo
|
en-US
Margins & Header/Footer
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl custom-prompt-prompt |
lij
Inserisci o testo pe-o fondo ò pe-a çimma
|
en-US
Enter your custom header/footer text
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-center-tip.tooltiptext |
lij
Çimma a-o centro
|
en-US
Center header
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-left-tip.tooltiptext |
lij
Çimma a-a mancinn-a
|
en-US
Left header
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-right-tip.tooltiptext |
lij
Çimma a-a drita
|
en-US
Right header
|
APIThese results are also available as an API request to search in
lij or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.