WPMU DEV in your language
Translations
Translation of Defender: English (South Africa)
| Prio | Original string | Translation | — |
|---|---|---|---|
| Block | Block | Details | |
| Sanitize | Sanitize | Details | |
| Deny | Deny | Details | |
| Sameorigin | Same-origin | Details | |
| Browser Caching | Browser Caching | Details | |
| Include Subdomains | Include Subdomains | Details | |
| If this optional parameter is specified, this rule applies to all of the site's subdomains as well. | If this optional parameter is specified, this rule applies to all of the site's subdomains as well. | Details | |
|
If this optional parameter is specified, this rule applies to all of the site's subdomains as well. If this optional parameter is specified, this rule applies to all of the site's subdomains as well.
Login to your account for contributing to translations.
|
|||
| Note: Do not include the preload directive by default if you maintain a project that provides HTTPS configuration advice or provides an option to enable HSTS. Be aware that inclusion in the preload list cannot easily be undone. Domains can be removed, but it takes months for a change. Check <a id="hsts-info-link" target="_blank" href="%s">here</a> for more information. | Note: Do not include the preload directive by default if you maintain a project that provides HTTPS configuration advice or provides an option to enable HSTS. Be aware that inclusion in the preload list cannot easily be undone. Domains can be removed, but it takes months for a change. Check here for more information. | Details | |
|
Note: Do not include the preload directive by default if you maintain a project that provides HTTPS configuration advice or provides an option to enable HSTS. Be aware that inclusion in the preload list cannot easily be undone. Domains can be removed, but it takes months for a change. Check <a id="hsts-info-link" target="_blank" href="%s">here</a> for more information. Note: Do not include the preload directive by default if you maintain a project that provides HTTPS configuration advice or provides an option to enable HSTS. Be aware that inclusion in the preload list cannot easily be undone. Domains can be removed, but it takes months for a change. Check here for more information.
Login to your account for contributing to translations.
|
|||
| Google maintains an HSTS preload service. By following the guidelines and successfully submitting your domain, browsers will never connect to your domain using an insecure connection. | Google maintains an HSTS preload service. By following the guidelines and successfully submitting your domain, browsers will never connect to your domain using an insecure connection. | Details | |
|
Google maintains an HSTS preload service. By following the guidelines and successfully submitting your domain, browsers will never connect to your domain using an insecure connection. Google maintains an HSTS preload service. By following the guidelines and successfully submitting your domain, browsers will never connect to your domain using an insecure connection.
Login to your account for contributing to translations.
|
|||
| HSTS Preload | HSTS Preload | Details | |
| The HTTP Strict-Transport-Security response header (HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. This is extremely important for websites that store and process sensitive information like ECommerce stores and helps prevent Protocol Downgrade and Clickjacking attacks. | The HTTP Strict-Transport-Security response header (HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. This is extremely important for websites that store and process sensitive information like ECommerce stores and helps prevent Protocol Downgrade and Clickjacking attacks. | Details | |
|
The HTTP Strict-Transport-Security response header (HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. This is extremely important for websites that store and process sensitive information like ECommerce stores and helps prevent Protocol Downgrade and Clickjacking attacks. The HTTP Strict-Transport-Security response header (HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. This is extremely important for websites that store and process sensitive information like ECommerce stores and helps prevent Protocol Downgrade and Clickjacking attacks.
Login to your account for contributing to translations.
|
|||
| Send a full URL (stripped from parameters) when performing a a same-origin or cross-origin request. | Send a full URL (stripped from parameters) when performing a same-origin or cross-origin request. | Details | |
|
Send a full URL (stripped from parameters) when performing a a same-origin or cross-origin request. Send a full URL (stripped from parameters) when performing a same-origin or cross-origin request.
Login to your account for contributing to translations.
|
|||
| Send a full URL when performing a same-origin request, only send the origin of the document to a-priori as-much-secure destination (HTTPS->HTTPS), and send no header to a less secure destination (HTTPS->HTTP). | Send a full URL when performing a same-origin request, only send the origin of the document to a-priori as-much-secure destination (HTTPS->HTTPS), and send no header to a less secure destination (HTTPS->HTTP). | Details | |
|
Send a full URL when performing a same-origin request, only send the origin of the document to a-priori as-much-secure destination (HTTPS->HTTPS), and send no header to a less secure destination (HTTPS->HTTP). Send a full URL when performing a same-origin request, only send the origin of the document to a-priori as-much-secure destination (HTTPS->HTTPS), and send no header to a less secure destination (HTTPS->HTTP).
Login to your account for contributing to translations.
|
|||
| Only send the origin of the document as the referrer to a-priori as-much-secure destination (HTTPS->HTTPS), but don't send it to a less secure destination (HTTPS->HTTP). | Only send the origin of the document as the referrer to a-priori as-much-secure destination (HTTPS->HTTPS), but don't send it to a less secure destination (HTTPS->HTTP). | Details | |
|
Only send the origin of the document as the referrer to a-priori as-much-secure destination (HTTPS->HTTPS), but don't send it to a less secure destination (HTTPS->HTTP). Only send the origin of the document as the referrer to a-priori as-much-secure destination (HTTPS->HTTPS), but don't send it to a less secure destination (HTTPS->HTTP).
Login to your account for contributing to translations.
|
|||
| A referrer will be sent for same-site origins, but cross-origin requests will contain no referrer information. | A referrer will be sent for same-site origins, but cross-origin requests will contain no referrer information. | Details | |
|
A referrer will be sent for same-site origins, but cross-origin requests will contain no referrer information. A referrer will be sent for same-site origins, but cross-origin requests will contain no referrer information.
Login to your account for contributing to translations.
|
|||
Export as •
Translators
- Melisa: 21.4%
- Lindeni Mahlalela: 13.7%