BETA

Transvision

Displaying 138 results for the string Header in en-US:

Entity en-US en-US
Entity # all locales browser • browser • aboutLogins.ftl
about-logins-import-dialog-error-file-format-description
en-US
Incorrect or missing column headers. Make sure the file includes columns for username, password and URL.
en-US
Incorrect or missing column headers. Make sure the file includes columns for username, password and URL.
Entity # all locales browser • browser • nsserrors.ftl
sec-error-cert-addr-mismatch
en-US
Address in signing certificate does not match address in message headers.
en-US
Address in signing certificate does not match address in message headers.
Entity # all locales browser • browser • preferences • siteDataSettings.ftl
site-data-removing-dialog.title
en-US
{ site-data-removing-header }
en-US
{ site-data-removing-header }
Entity # all locales devtools • client • jsonview.properties
jsonViewer.requestHeaders
en-US
Request Headers
en-US
Request Headers
Entity # all locales devtools • client • jsonview.properties
jsonViewer.responseHeaders
en-US
Response Headers
en-US
Response Headers
Entity # all locales devtools • client • jsonview.properties
jsonViewer.tab.Headers
en-US
Headers
en-US
Headers
Entity # all locales devtools • client • netmonitor.properties
headersEmptyText
en-US
No headers for this request
en-US
No headers for this request
Entity # all locales devtools • client • netmonitor.properties
headersFilterText
en-US
Filter Headers
en-US
Filter Headers
Entity # all locales devtools • client • netmonitor.properties
netmonitor.context.copyRequestHeaders
en-US
Copy Request Headers
en-US
Copy Request Headers
Entity # all locales devtools • client • netmonitor.properties
netmonitor.context.copyResponseHeaders
en-US
Copy Response Headers
en-US
Copy Response Headers
Entity # all locales devtools • client • netmonitor.properties
netmonitor.custom.headers
en-US
Request Headers
en-US
Request Headers
Entity # all locales devtools • client • netmonitor.properties
netmonitor.tab.headers
en-US
Headers
en-US
Headers
Entity # all locales devtools • client • netmonitor.properties
netmonitor.toolbar.responseHeaders
en-US
Response Headers
en-US
Response Headers
Entity # all locales devtools • client • netmonitor.properties
requestHeaders
en-US
Request Headers
en-US
Request Headers
Entity # all locales devtools • client • netmonitor.properties
requestHeadersFromUpload
en-US
Request headers from upload stream
en-US
Request headers from upload stream
Entity # all locales devtools • client • netmonitor.properties
responseHeaders
en-US
Response Headers
en-US
Response Headers
Entity # all locales dom • chrome • accessibility • AccessFu.properties
columnheader
en-US
column header
en-US
column header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
columnheaderAbbr
en-US
column header
en-US
column header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
header
en-US
header
en-US
header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
headerAbbr
en-US
header
en-US
header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
rowheader
en-US
row header
en-US
row header
Entity # all locales dom • chrome • accessibility • AccessFu.properties
rowheaderAbbr
en-US
row header
en-US
row header
Entity # all locales dom • chrome • dom • dom.properties
ForbiddenHeaderWarning
en-US
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
en-US
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
en-US
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
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.
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
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.
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
en-US
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
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.
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
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.
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
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.
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
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.
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
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.
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
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.
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
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.
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
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.
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
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’).
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
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’).
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
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’).
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
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’).
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
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’).
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
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).
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
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).
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
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).
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
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 ‘*’).
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
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).
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
Reporting Header: invalid JSON value received.
en-US
Reporting Header: invalid JSON value received.
Entity # all locales dom • chrome • security • security.properties
ReportingHeaderInvalidNameItem
en-US
Reporting Header: invalid name for group.
en-US
Reporting Header: invalid name for group.
Entity # all locales dom • chrome • security • security.properties
ReportingHeaderInvalidURLEndpoint
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
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
en-US
Header
en-US
Header
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.header.help
en-US
Toggles visibility of the header bar.
en-US
Toggles visibility of the header bar.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.header.label
en-US
Header
en-US
Header
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.sync-header.help
en-US
Synchronizes all views with their current header display setting.
en-US
Synchronizes all views with their current header display setting.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.toggle-ui.help
en-US
Toggles the visibility of various pieces of the user interface. <thing> must be one of: tabstrip, userlist, header, status.
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
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.
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
en-US
Show header
en-US
Show header
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.group.global.header.help
en-US
Sets the default visibility for headers of views. Each view can override this default if necessary.
en-US
Sets the default visibility for headers of views. Each view can override this default if necessary.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.group.global.header.label
en-US
Headers
en-US
Headers
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.outputWindowURL.help
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!
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
en-US
New message header:
en-US
New message header:
Entity # all locales mail • chrome • messenger • CustomHeaders.dtd
window.title
en-US
Customize Headers
en-US
Customize Headers
Entity # all locales mail • chrome • messenger • addressbook • abCard.dtd
preferDisplayName.label
en-US
Always prefer display name over message header
en-US
Always prefer display name over message header
Entity # all locales mail • chrome • messenger • am-junk.dtd
ispHeaders.label
en-US
Trust junk mail headers set by:
en-US
Trust junk mail headers set by:
Entity # all locales mail • chrome • messenger • am-main.dtd
catchAll.label
en-US
Reply from this identity when delivery headers match:
en-US
Reply from this identity when delivery headers match:
Entity # all locales mail • chrome • messenger • am-server-top.dtd
headersOnly.label
en-US
Fetch headers only
en-US
Fetch headers only
Entity # all locales mail • chrome • messenger • custom.properties
colonInHeaderName
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.
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 • downloadheaders.dtd
all.label
en-US
Download all headers
en-US
Download all headers
Entity # all locales mail • chrome • messenger • downloadheaders.dtd
headers.label
en-US
headers
en-US
headers
Entity # all locales mail • chrome • messenger • downloadheaders.dtd
mark.label
en-US
Mark remaining headers as read
en-US
Mark remaining headers as read
Entity # all locales mail • chrome • messenger • filter.properties
customHeaderOverflow
en-US
You've exceeded the limit of 50 custom headers. Please remove one or more custom headers and try again.
en-US
You've exceeded the limit of 50 custom headers. Please remove one or more custom headers and try again.
Entity # all locales mail • chrome • messenger • filter.properties
filterCustomHeaderOverflow
en-US
Your filters have exceeded the limit of 50 custom headers. Please edit the msgFilterRules.dat file, which contains your filters, to use fewer custom headers.
en-US
Your filters have exceeded the limit of 50 custom headers. Please edit the msgFilterRules.dat file, which contains your filters, to use fewer custom headers.
Entity # all locales mail • chrome • messenger • filter.properties
invalidCustomHeader
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.
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
en-US
Downloading message header %1$S of %2$S in %3$S
en-US
Downloading message header %1$S of %2$S in %3$S
Entity # all locales mail • chrome • messenger • localMsgs.properties
pop3ServerDoesNotSupportTopCommand
en-US
The POP3 mail server (%S) does not support the TOP command. Without server support for this, we cannot implement the ``Maximum Message Size'' or ``Fetch Headers Only'' preference. This option has been disabled, and messages will be downloaded regardless of their size.
en-US
The POP3 mail server (%S) does not support the TOP command. Without server support for this, we cannot implement the ``Maximum Message Size'' or ``Fetch Headers Only'' preference. This option has been disabled, and messages will be downloaded regardless of their size.
Entity # all locales mail • chrome • messenger • localMsgs.properties
pop3ServerDoesNotSupportUidlEtc
en-US
The POP3 mail server (%S) does not support UIDL or XTND XLST, which are required to implement the ``Leave on Server'', ``Maximum Message Size'' or ``Fetch Headers Only'' options. To download your mail, turn off these options in the Server Settings for your mail server in the Account Settings window.
en-US
The POP3 mail server (%S) does not support UIDL or XTND XLST, which are required to implement the ``Leave on Server'', ``Maximum Message Size'' or ``Fetch Headers Only'' options. To download your mail, turn off these options in the Server Settings for your mail server in the Account Settings window.
Entity # all locales mail • chrome • messenger • messenger.dtd
headersMenu.label
en-US
Headers
en-US
Headers
Entity # all locales mail • chrome • messenger • messengercompose • EditorTableProperties.dtd
cellHeader.label
en-US
Header
en-US
Header
Entity # all locales mail • chrome • messenger • mime.properties
MIME_MSG_PARTIAL_NOT_DOWNLOADED_EXPLANATION
en-US
Only the headers for this message were downloaded from the mail server.
en-US
Only the headers for this message were downloaded from the mail server.
Entity # all locales mail • chrome • messenger • news.properties
downloadHeadersInfoText
en-US
There are %S new message headers to download for this newsgroup.
en-US
There are %S new message headers to download for this newsgroup.
Entity # all locales mail • chrome • messenger • news.properties
downloadHeadersTitlePrefix
en-US
Download Headers
en-US
Download Headers
Entity # all locales mail • chrome • messenger • news.properties
newNewsgroupFilteringHeaders
en-US
Getting headers for filters: %1$S (%2$S/%3$S) on %4$S
en-US
Getting headers for filters: %1$S (%2$S/%3$S) on %4$S
Entity # all locales mail • chrome • messenger • news.properties
newNewsgroupHeaders
en-US
Downloading %1$S of %2$S headers for %3$S
en-US
Downloading %1$S of %2$S headers for %3$S
Entity # all locales mail • messenger • openpgp • msgReadStatus.ftl
message-security-button.title
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 }) }
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
en-US
Show Header
en-US
Show Header
Entity # all locales security • manager • chrome • pipnss • nsserrors.properties
SEC_ERROR_CERT_ADDR_MISMATCH
en-US
Address in signing certificate does not match address in message headers.
en-US
Address in signing certificate does not match address in message headers.
Entity # all locales suite • chrome • editor • dialogs • EditorTableProperties.dtd
cellHeader.label
en-US
Header
en-US
Header
Entity # all locales suite • chrome • mailnews • CustomHeaders.dtd
newMsgHeader.label
en-US
New message header:
en-US
New message header:
Entity # all locales suite • chrome • mailnews • CustomHeaders.dtd
window.title
en-US
Customize Headers
en-US
Customize Headers
Entity # all locales suite • chrome • mailnews • addressbook • abCardOverlay.dtd
preferDisplayName.label
en-US
Always prefer display name over message header
en-US
Always prefer display name over message header
Entity # all locales suite • chrome • mailnews • custom.properties
colonInHeaderName
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.
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 • downloadheaders.dtd
all.label
en-US
Download all headers
en-US
Download all headers
Entity # all locales suite • chrome • mailnews • downloadheaders.dtd
headers.label
en-US
headers
en-US
headers
Entity # all locales suite • chrome • mailnews • downloadheaders.dtd
mark.label
en-US
Mark remaining headers as read
en-US
Mark remaining headers as read
Entity # all locales suite • chrome • mailnews • filter.properties
customHeaderOverflow
en-US
You've exceeded the limit of 50 custom headers. Please remove one or more custom headers and try again.
en-US
You've exceeded the limit of 50 custom headers. Please remove one or more custom headers and try again.
Entity # all locales suite • chrome • mailnews • filter.properties
filterCustomHeaderOverflow
en-US
Your filters have exceeded the limit of 50 custom headers. Please edit the msgFilterRules.dat file, which contains your filters, to use fewer custom headers.
en-US
Your filters have exceeded the limit of 50 custom headers. Please edit the msgFilterRules.dat file, which contains your filters, to use fewer custom headers.
Entity # all locales suite • chrome • mailnews • filter.properties
invalidCustomHeader
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.
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
en-US
Downloading message header %1$S of %2$S in %3$S
en-US
Downloading message header %1$S of %2$S in %3$S
Entity # all locales suite • chrome • mailnews • localMsgs.properties
pop3ServerDoesNotSupportTopCommand
en-US
The POP3 mail server (%S) does not support the TOP command. Without server support for this, we cannot implement the ``Maximum Message Size'' or ``Fetch Headers Only'' preference. This option has been disabled, and messages will be downloaded regardless of their size.
en-US
The POP3 mail server (%S) does not support the TOP command. Without server support for this, we cannot implement the ``Maximum Message Size'' or ``Fetch Headers Only'' preference. This option has been disabled, and messages will be downloaded regardless of their size.
Entity # all locales suite • chrome • mailnews • localMsgs.properties
pop3ServerDoesNotSupportUidlEtc
en-US
The POP3 mail server (%S) does not support UIDL or XTND XLST, which are required to implement the ``Leave on Server'', ``Maximum Message Size'' or ``Fetch Headers Only'' options. To download your mail, turn off these options in the Server Settings for your mail server in the Account Settings window.
en-US
The POP3 mail server (%S) does not support UIDL or XTND XLST, which are required to implement the ``Leave on Server'', ``Maximum Message Size'' or ``Fetch Headers Only'' options. To download your mail, turn off these options in the Server Settings for your mail server in the Account Settings window.
Entity # all locales suite • chrome • mailnews • messenger.dtd
headersMenu.label
en-US
Headers
en-US
Headers
Entity # all locales suite • chrome • mailnews • mime.properties
MIME_MSG_PARTIAL_NOT_DOWNLOADED_EXPLANATION
en-US
Only the headers for this message were downloaded from the mail server.
en-US
Only the headers for this message were downloaded from the mail server.
Entity # all locales suite • chrome • mailnews • news.properties
downloadHeadersInfoText
en-US
There are %S new message headers to download for this newsgroup.
en-US
There are %S new message headers to download for this newsgroup.
Entity # all locales suite • chrome • mailnews • news.properties
downloadHeadersTitlePrefix
en-US
Download Headers
en-US
Download Headers
Entity # all locales suite • chrome • mailnews • news.properties
newNewsgroupFilteringHeaders
en-US
Getting headers for filters: %1$S (%2$S/%3$S) on %4$S
en-US
Getting headers for filters: %1$S (%2$S/%3$S) on %4$S
Entity # all locales suite • chrome • mailnews • news.properties
newNewsgroupHeaders
en-US
Downloading %1$S of %2$S headers on %3$S
en-US
Downloading %1$S of %2$S headers on %3$S
Entity # all locales suite • chrome • mailnews • pref • am-junk.dtd
ispHeaders.label
en-US
Trust junk mail headers set by:
en-US
Trust junk mail headers set by:
Entity # all locales suite • chrome • mailnews • pref • am-main.dtd
catchAll.label
en-US
Reply from this identity when delivery headers match:
en-US
Reply from this identity when delivery headers match:
Entity # all locales suite • chrome • mailnews • pref • am-server-top.dtd
headersOnly.label
en-US
Fetch headers only
en-US
Fetch headers only
Entity # all locales suite • chrome • mailnews • pref • pref-composing_messages.dtd
noReplyOption.label
en-US
No Reply Header
en-US
No Reply Header
Entity # all locales suite • chrome • mailnews • pref • pref-composing_messages.dtd
selectHeaderType.label
en-US
Select reply header type:
en-US
Select reply header type:
Entity # all locales toolkit • chrome • global • printdialog.properties
customHeaderFooterPrompt
en-US
Please enter your custom header/footer text
en-US
Please enter your custom header/footer text
Entity # all locales toolkit • chrome • global • printdialog.properties
headerFooter
en-US
Header and Footer
en-US
Header and Footer
Entity # all locales toolkit • chrome • global • printdialog.properties
pageHeadersTitleMac
en-US
Page Headers:
en-US
Page Headers:
Entity # all locales toolkit • chrome • global • printdialog.properties
summaryHeaderTitle
en-US
Page Headers
en-US
Page Headers
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
advanced-tab.label
en-US
Margins & Header/Footer
en-US
Margins & Header/Footer
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
custom-prompt-prompt
en-US
Enter your custom header/footer text
en-US
Enter your custom header/footer text
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
header-center-tip.tooltiptext
en-US
Center header
en-US
Center header
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
header-footer-label.value
en-US
Headers & Footers
en-US
Headers & Footers
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
header-left-tip.tooltiptext
en-US
Left header
en-US
Left header
Entity # all locales toolkit • toolkit • printing • printDialogs.ftl
header-right-tip.tooltiptext
en-US
Right header
en-US
Right header
Entity # all locales toolkit • toolkit • printing • printUI.ftl
printui-headers-footers-checkbox
en-US
Print headers and footers
en-US
Print headers and footers
Please enable JavaScript. Some features won't be available without it.