New to Translating WordPress? Read through our Translator Handbook to get started. Hide
Prio | Original string | Translation | — |
---|---|---|---|
↑ | Limit access to visitors who are logged in or allowed by IP addresses. Includes many options for handling blocked visitors. | You have to log in to add a translation. | Details |
Original untranslated
Limit access to visitors who are logged in or allowed by IP addresses. Includes many options for handling blocked visitors.
You have to log in to edit this translation. |
|||
↑ | Restricted Site Access | You have to log in to add a translation. | Details |
Original untranslated |
|||
This will then only use the <code>REMOTE_ADDR</code> HTTP header to determine the IP address of the visitor. This header can't be spoofed, so this will increase security. Note that this is now the default for all new installs since version 7.5.0. | You have to log in to add a translation. | Details | |
Original untranslated
This will then only use the <code>REMOTE_ADDR</code> HTTP header to determine the IP address of the visitor. This header can't be spoofed, so this will increase security. Note that this is now the default for all new installs since version 7.5.0.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
In 7.3.2, two new filters were added that can be utilized to help prevent IP spoofing attacks. The first filter allows you to set up a list of approved proxy IP addresses and the second allows you to set up a list of approved HTTP headers. For any sites that were using Restricted Site Access prior to version 7.5.0, a handful of HTTP headers are trusted by default. To change this, utilize the <code>rsa_trusted_headers</code> filter to modify the HTTP headers you want to trust. If your site is not running behind a proxy, we recommend doing the following: | You have to log in to add a translation. | Details | |
Original untranslated
In 7.3.2, two new filters were added that can be utilized to help prevent IP spoofing attacks. The first filter allows you to set up a list of approved proxy IP addresses and the second allows you to set up a list of approved HTTP headers. For any sites that were using Restricted Site Access prior to version 7.5.0, a handful of HTTP headers are trusted by default. To change this, utilize the <code>rsa_trusted_headers</code> filter to modify the HTTP headers you want to trust. If your site is not running behind a proxy, we recommend doing the following:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
When this option is activated, it serves as a barrier to all visitors except those who are authenticated (logged in) or whose IP addresses are included in the 'Unrestricted IP addresses' setting. This restriction applies universally, even to automated crawlers such as search engines. | You have to log in to add a translation. | Details | |
Original untranslated
When this option is activated, it serves as a barrier to all visitors except those who are authenticated (logged in) or whose IP addresses are included in the 'Unrestricted IP addresses' setting. This restriction applies universally, even to automated crawlers such as search engines.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
When the 'Discourage search engines from indexing this site' option is enabled, it prevents search engines from indexing the site while still permitting access to regular visitors. | You have to log in to add a translation. | Details | |
Original untranslated
When the 'Discourage search engines from indexing this site' option is enabled, it prevents search engines from indexing the site while still permitting access to regular visitors.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
What does 'Restrict site access to visitors who are logged in or allowed by IP address' do? | You have to log in to add a translation. | Details | |
Original untranslated
What does 'Restrict site access to visitors who are logged in or allowed by IP address' do?
CommentFound in faq header. You have to log in to edit this translation. |
|||
What does 'Discourage search engines from indexing this site' do? | You have to log in to add a translation. | Details | |
Original untranslated
What does 'Discourage search engines from indexing this site' do?
CommentFound in faq header. You have to log in to edit this translation. |
|||
If your proxy does not use static IP addresses, you can still utilize the <code>rsa_trusted_headers</code> filter to change which HTTP headers you want to trust. | You have to log in to add a translation. | Details | |
Original untranslated
If your proxy does not use static IP addresses, you can still utilize the <code>rsa_trusted_headers</code> filter to change which HTTP headers you want to trust.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
And then use the <code>rsa_trusted_headers</code> filter to set which HTTP headers you want to trust. Consult with your proxy provider to determine which header(s) they use to hold the original client IP: | You have to log in to add a translation. | Details | |
Original untranslated
And then use the <code>rsa_trusted_headers</code> filter to set which HTTP headers you want to trust. Consult with your proxy provider to determine which header(s) they use to hold the original client IP:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
If your site is running behind a proxy (like a CDN), you usually can't rely on the <code>REMOTE_ADDR</code> HTTP header, as this will contain the IP address of the proxy, not the user. If your proxy uses static IP addresses, we recommend using the <code>rsa_trusted_proxies</code> filter to set those trusted IP addresses: | You have to log in to add a translation. | Details | |
Original untranslated
If your site is running behind a proxy (like a CDN), you usually can't rely on the <code>REMOTE_ADDR</code> HTTP header, as this will contain the IP address of the proxy, not the user. If your proxy uses static IP addresses, we recommend using the <code>rsa_trusted_proxies</code> filter to set those trusted IP addresses:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Please note that setting <code>RSA_FORCE_RESTRICTION</code> will override <code>RSA_FORBID_RESTRICTION</code> if both are set. | You have to log in to add a translation. | Details | |
Original untranslated
Please note that setting <code>RSA_FORCE_RESTRICTION</code> will override <code>RSA_FORBID_RESTRICTION</code> if both are set.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Make sure you add it before the <code>/* That's all, stop editing! Happy blogging. */</code> line. | You have to log in to add a translation. | Details | |
Original untranslated
Make sure you add it before the <code>/* That's all, stop editing! Happy blogging. */</code> line.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Or to ensure your site won't be in restricted mode: | You have to log in to add a translation. | Details | |
Original untranslated
Or to ensure your site won't be in restricted mode:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
You can force the plugin to be in restricted mode by adding the following to your <code>wp-config.php</code> file: | You have to log in to add a translation. | Details | |
Original untranslated
You can force the plugin to be in restricted mode by adding the following to your <code>wp-config.php</code> file:
CommentFound in faq paragraph. You have to log in to edit this translation. |
Export as
Comment
Short description.