Skip to content

Commit c6c4613

Browse files
committed
Added missing content to Get Started
1 parent fb62a49 commit c6c4613

File tree

1 file changed

+35
-0
lines changed

1 file changed

+35
-0
lines changed

src/content/docs/privacy-proxy/privacy-proxy.mdx

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,3 +8,38 @@ head:
88
content: Get started with Cloudflare Privacy Proxy
99
Description:
1010
---
11+
## Environments
12+
13+
Cloudflare will provide access to both development and production environments.
14+
Credentials are shared across both environments.
15+
16+
<table-wrap>
17+
18+
| **Environment** | **Endpoint** | **Description** |
19+
|-------------------|----------------------------------|-------------------------------------------------------------------------------------------------|
20+
| Dev token issuer | `test-pat.issuer.cloudflare.com` | Development token issuance environment - Use for internal development, integration testing, and end-to-end validation. Cloudflare recommends the Go, Rust, and TypeScript implementations of RFC 9578, and provides a [test website](https://pepe-debug.research.cloudflare.com/) to test your attester against. |
21+
| Dev Privacy Proxy | `test-proxy.cloudflare.com` | Development proxy environment – This is subject to change and Cloudflare recommends making this configuration dynamic to support multiple environments, including canary releases and internal employee testing. |
22+
23+
</table-wrap>
24+
25+
:::note
26+
27+
Any load testing needs to be communicated to Cloudflare in advance, regardless of environment. Both environments run on the Cloudlfare global production edge network and do not differentiate on network topology or prioritization.
28+
29+
:::
30+
31+
### Proxy authentication
32+
33+
The Privacy Proxy Ingress service authenticates to clients using standard WebPKI-based X.509 certificates in TLS, with a certificate rooted in DigiCert.
34+
35+
### Example client code
36+
37+
Cloudflare will provide access to a MASQUE client, which can be used in mobile client code to connect to the MASQUE proxy provided by Cloudflare. For example:
38+
39+
```sh
40+
cargo run --bin quiche-client -- \
41+
--no-verify \
42+
--connect-to test-proxy.cloudflare.com \
43+
--connect-type=HTTP \
44+
https://example.com
45+
```

0 commit comments

Comments
 (0)