BETA

Transvision

Warning: the current search includes leading or trailing whitespaces.
Click here to perform the same search without whitespaces.

Displaying 49 results for the string HTTP in en-US:

Entity en-US en-US
Entity # all locales android_l10n • mozilla-mobile • android-components • components • browser • errorpages • src • main • res • values • strings.xml
mozac_browser_errorpages_httpsonly_button
en-US
Continue to HTTP Site
en-US
Continue to HTTP Site
Entity # all locales android_l10n • mozilla-mobile • android-components • components • browser • errorpages • src • main • res • values • strings.xml
mozac_browser_errorpages_security_bad_hsts_cert_techInfo2
en-US
<label> <b>%1$s</b> has a security policy called HTTP Strict Transport Security (HSTS), which means that <b>%2$s</b> can only connect to it securely. You can’t add an exception to visit this site. </label>
en-US
<label> <b>%1$s</b> has a security policy called HTTP Strict Transport Security (HSTS), which means that <b>%2$s</b> can only connect to it securely. You can’t add an exception to visit this site. </label>
Entity # all locales mail • messenger • preferences • connection.ftl
proxy-http-label.value
en-US
HTTP Proxy:
en-US
HTTP Proxy:
Entity # all locales suite • chatzilla • chrome • chatzilla.properties
pref.proxy.typeOverride.help
en-US
Override the normal proxy choice by specifying "http" to use your browser's HTTP Proxy or "none" to force no proxy to be used (not even the SOCKS proxy). Note that this usually only works when the browser is set to use a manual proxy configuration.
en-US
Override the normal proxy choice by specifying "http" to use your browser's HTTP Proxy or "none" to force no proxy to be used (not even the SOCKS proxy). Note that this usually only works when the browser is set to use a manual proxy configuration.
Entity # all locales suite • chrome • common • permissions • cookieViewer.properties
allowedURLSchemes
en-US
Check the entered url. Also you can only add permissions for http or https schemes
en-US
Check the entered url. Also you can only add permissions for http or https schemes
Entity # all locales suite • chrome • common • pref • pref-http.dtd
pref.http.title
en-US
HTTP Networking
en-US
HTTP Networking
Entity # all locales suite • chrome • common • pref • pref-http.dtd
prefEnableHTTP10.label
en-US
Use HTTP 1.0
en-US
Use HTTP 1.0
Entity # all locales suite • chrome • common • pref • pref-http.dtd
prefEnableHTTP11.label
en-US
Use HTTP 1.1
en-US
Use HTTP 1.1
Entity # all locales suite • chrome • common • pref • pref-http.dtd
prefPara
en-US
HTTP connections may be fine-tuned using these options to enhance either performance or compatibility. Some proxy servers, for example, are known to require HTTP/1.0 (see the release notes for details).
en-US
HTTP connections may be fine-tuned using these options to enhance either performance or compatibility. Some proxy servers, for example, are known to require HTTP/1.0 (see the release notes for details).
Entity # all locales suite • chrome • common • pref • pref-proxies-advanced.dtd
http.label
en-US
HTTP Proxy:
en-US
HTTP Proxy:
Entity # all locales suite • chrome • common • pref • pref-proxies-advanced.dtd
reuseProxy.label
en-US
Use HTTP Proxy settings for all protocols
en-US
Use HTTP Proxy settings for all protocols
Entity # all locales suite • chrome • common • pref • preferences.dtd
httpnetworking.label
en-US
HTTP Networking
en-US
HTTP Networking
Entity # all locales suite • chrome • editor • dialogs • EditorPublish.dtd
browseUrl.label
en-US
HTTP address of your homepage (e.g.: 'http://www.myisp.com/myusername'):
en-US
HTTP address of your homepage (e.g.: 'http://www.myisp.com/myusername'):
Entity # all locales firefox_ios • firefox-ios.xliff
b019131d32b3acecea11ca209e868d52
en-US
Only HTTP and HTTPS links can be shared.
en-US
Only HTTP and HTTPS links can be shared.
Entity # all locales browser • browser • firefoxRelay.ftl
firefox-relay-get-reusable-masks-failed
en-US
{ -relay-brand-name } could not find reusable masks. HTTP error code: { $status }.
en-US
{ -relay-brand-name } could not find reusable masks. HTTP error code: { $status }.
Entity # all locales browser • browser • firefoxRelay.ftl
firefox-relay-mask-generation-failed
en-US
{ -relay-brand-name } could not generate a new mask. HTTP error code: { $status }.
en-US
{ -relay-brand-name } could not generate a new mask. HTTP error code: { $status }.
Entity # all locales browser • browser • preferences • connection.ftl
connection-proxy-http
en-US
HTTP Proxy
en-US
HTTP Proxy
Entity # all locales browser • chrome • browser • downloads • downloads.properties
unblockInsecure2
en-US
The download is offered over HTTP even though the current document was delivered over a secure HTTPS connection. If you proceed, the download may be corrupted or tampered with during the download process.
en-US
The download is offered over HTTP even though the current document was delivered over a secure HTTPS connection. If you proceed, the download may be corrupted or tampered with during the download process.
Entity # all locales devtools • client • netmonitor.properties
netmonitor.security.hsts
en-US
HTTP Strict Transport Security:
en-US
HTTP Strict Transport Security:
Entity # all locales devtools • client • netmonitor.properties
netmonitor.toolbar.disableCache.tooltip
en-US
Disable HTTP cache
en-US
Disable HTTP cache
Entity # all locales devtools • client • toolbox-options.ftl
options-disable-http-cache-label
en-US
Disable HTTP Cache (when toolbox is open)
en-US
Disable HTTP Cache (when toolbox is open)
Entity # all locales devtools • client • toolbox-options.ftl
options-disable-http-cache-tooltip.title
en-US
Turning this option on will disable the HTTP cache for all tabs that have the toolbox open. Service Workers are not affected by this option.
en-US
Turning this option on will disable the HTTP cache for all tabs that have the toolbox open. Service Workers are not affected by this option.
Entity # all locales devtools • client • toolbox-options.ftl
options-enable-service-workers-http-label
en-US
Enable Service Workers over HTTP (when toolbox is open)
en-US
Enable Service Workers over HTTP (when toolbox is open)
Entity # all locales devtools • client • toolbox-options.ftl
options-enable-service-workers-http-tooltip.title
en-US
Turning this option on will enable the service workers over HTTP for all tabs that have the toolbox open.
en-US
Turning this option on will enable the service workers over HTTP for all tabs that have the toolbox open.
Entity # all locales dom • chrome • dom • dom.properties
MediaLoadHttpError
en-US
HTTP load failed with status %1$S. Load of media resource %2$S failed.
en-US
HTTP load failed with status %1$S. Load of media resource %2$S failed.
Entity # all locales dom • chrome • dom • dom.properties
MediaLoadUnsupportedMimeType
en-US
HTTP “Content-Type” of “%1$S” is not supported. Load of media resource %2$S failed.
en-US
HTTP “Content-Type” of “%1$S” is not supported. Load of media resource %2$S failed.
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 • layout • htmlparser.properties
EncDetectorReload
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncDetectorReloadPlain
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncErrorFrame
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncErrorFramePlain
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDecl
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclPlain
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
Entity # all locales dom • chrome • security • csp.properties
reportURInotHttpsOrHttp2
en-US
The report URI (%1$S) should be an HTTP or HTTPS URI.
en-US
The report URI (%1$S) should be an HTTP or HTTPS URI.
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 netwerk • necko.properties
InvalidHTTPResponseStatusLine
en-US
The status line of the HTTP response is invalid
en-US
The status line of the HTTP response is invalid
Entity # all locales security • manager • chrome • pipnss • nsserrors.properties
SEC_ERROR_BAD_HTTP_RESPONSE
en-US
Server returned bad HTTP response
en-US
Server returned bad HTTP response
Entity # all locales security • manager • chrome • pipnss • nsserrors.properties
SEC_ERROR_OCSP_BAD_HTTP_RESPONSE
en-US
The OCSP server returned unexpected/invalid HTTP data.
en-US
The OCSP server returned unexpected/invalid HTTP data.
Entity # all locales toolkit • toolkit • about • aboutHttpsOnlyError.ftl
about-httpsonly-button-continue-to-site
en-US
Continue to HTTP Site
en-US
Continue to HTTP Site
Entity # all locales toolkit • toolkit • about • aboutLogging.ftl
about-logging-log-tutorial
en-US
See <a data-l10n-name="logging">HTTP Logging</a> for instructions on how to use this tool.
en-US
See <a data-l10n-name="logging">HTTP Logging</a> for instructions on how to use this tool.
Entity # all locales toolkit • toolkit • about • aboutNetworking.ftl
about-networking-dns-https-rr-lookup-table-column
en-US
HTTP RRs
en-US
HTTP RRs
Entity # all locales toolkit • toolkit • about • aboutNetworking.ftl
about-networking-http-clear-cache-button
en-US
Clear HTTP Cache
en-US
Clear HTTP Cache
Entity # all locales toolkit • toolkit • about • aboutNetworking.ftl
about-networking-http-version
en-US
HTTP Version
en-US
HTTP Version
Entity # all locales toolkit • toolkit • neterror • certError.ftl
cert-error-details-hsts-label
en-US
HTTP Strict Transport Security: { $hasHSTS }
en-US
HTTP Strict Transport Security: { $hasHSTS }
Entity # all locales toolkit • toolkit • neterror • certError.ftl
cert-error-details-key-pinning-label
en-US
HTTP Public Key Pinning: { $hasHPKP }
en-US
HTTP Public Key Pinning: { $hasHPKP }
Entity # all locales toolkit • toolkit • neterror • netError.ftl
certerror-what-should-i-do-bad-sts-cert-explanation
en-US
<b>{ $hostname }</b> has a security policy called HTTP Strict Transport Security (HSTS), which means that { -brand-short-name } can only connect to it securely. You can’t add an exception to visit this site.
en-US
<b>{ $hostname }</b> has a security policy called HTTP Strict Transport Security (HSTS), which means that { -brand-short-name } can only connect to it securely. You can’t add an exception to visit this site.
Entity # all locales toolkit • toolkit • neterror • nsserrors.ftl
sec-error-bad-http-response
en-US
Server returned bad HTTP response
en-US
Server returned bad HTTP response
Entity # all locales toolkit • toolkit • neterror • nsserrors.ftl
sec-error-ocsp-bad-http-response
en-US
The OCSP server returned unexpected/invalid HTTP data.
en-US
The OCSP server returned unexpected/invalid HTTP data.
Please enable JavaScript. Some features won't be available without it.