Skip to content

Commit 5079b91

Browse files
authored
add htaccess auth docs (#30577)
1 parent 992042f commit 5079b91

File tree

1 file changed

+4
-0
lines changed
  • packages/gatsby-source-wordpress/docs/features

1 file changed

+4
-0
lines changed

packages/gatsby-source-wordpress/docs/features/security.md

+4
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,8 @@ If you have a requirement where you need some private data in Gatsby, you should
77
1. If your private data requirements are related to specific user accounts and will require different data depending on who's logged in to your site, add client-side authentication and make live GraphQL requests to WPGraphQL in-browser (using [Apollo](https://www.apollographql.com/docs/react/) or similar).
88
2. Filter your data to be public in WPGraphQL. If you need some data during a Gatsby build, you need to consider it as public data. This means you need to make it public in WPGraphQL. Think very carefully before you do this, and make sure you understand the security implications before you change anything. To filter private data to make it public, visit the [WPGraphQL docs](https://www.wpgraphql.com/recipes/making-menus-and-menu-items-public/) to learn more.
99

10+
## Using htaccess auth
11+
12+
htaccess auth (sometimes referred to as basic auth or privacy mode) is a server-level security mechanism for restricting all access to your WordPress install. In this case, htaccess would block access to your site during build time. To fix this, [use the htaccess plugin options](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-wordpress/docs/plugin-options.md#authhtaccess) to enable this plugin to access your protected WordPress install.
13+
1014
:point_left: [Back to Features](./index.md)

0 commit comments

Comments
 (0)