@@ -132,42 +132,3 @@ You will need to update your CAA records to allow us to issue the certificate.
132
132
If your custom domain was previously used in GitBook, contact GitBook support (via live chat in their website)
133
133
to remove the domain name from their DNS Zone in order for your domain name to work with Read the Docs,
134
134
else it will always redirect to GitBook.
135
-
136
- Proxy SSL
137
- ---------
138
-
139
- .. warning ::
140
-
141
- This option is deprecated,
142
- we already issue SSL certificates for all domains.
143
-
144
- If you would prefer to do your own SSL termination
145
- on a server you own and control,
146
- you can do that although the setup is a bit more complex.
147
-
148
- Broadly, the steps are:
149
-
150
- * Have a server listening on 443 that you control
151
- * Procure an SSL certificate for your domain and provision it
152
- and the private key on your server.
153
- * Add a domain that you wish to point at Read the Docs
154
- * Enable proxying to us, with a custom ``X-RTD-SLUG `` header
155
-
156
- An example nginx configuration for pip would look like:
157
-
158
- .. code-block :: nginx
159
- :emphasize-lines: 9
160
-
161
- server {
162
- server_name pip.pypa.io;
163
- location / {
164
- proxy_pass https://pip.readthedocs.io:443;
165
- proxy_set_header Host $http_host;
166
- proxy_set_header X-Forwarded-Proto https;
167
- proxy_set_header X-Real-IP $remote_addr;
168
- proxy_set_header X-Scheme $scheme;
169
- proxy_set_header X-RTD-SLUG pip;
170
- proxy_connect_timeout 10s;
171
- proxy_read_timeout 20s;
172
- }
173
- }
0 commit comments