Optional, but this might be nicer in a second example Caddyfile or a note in the readme / docs somewhere
+11
-1
Diff
round #0
+11
-1
Caddyfile
+11
-1
Caddyfile
···
1
1
{$PDS_HOSTNAME}, *.{$PDS_HOSTNAME} {
2
-
reverse_proxy pds:8008
2
+
# See https://gist.github.com/mary-ext/6e27b24a83838202908808ad528b3318#method-5-self-hosted-pds
3
+
handle /xrpc/app.bsky.ageassurance.getState {
4
+
header content-type "application/json"
5
+
header access-control-allow-headers "authorization,dpop,atproto-accept-labelers,atproto-proxy"
6
+
header access-control-allow-origin "*"
7
+
respond `{"state":{"lastInitiatedAt":"2025-07-14T14:22:43.912Z","status":"assured","access":"full"},"metadata":{"accountCreatedAt":"2022-11-17T00:35:16.391Z"}}` 200
8
+
}
9
+
10
+
handle {
11
+
reverse_proxy pds:8008
12
+
}
3
13
}
History
1 round
3 comments
expand 3 comments
Yeah, that's fair. Any idea where a good location might be or just leave people to find it if they need it?
I think most people who might need it will end up finding out about it via bluesky
closed without merging
I've tried to avoid bluesky-specific behaviour wherever possible, so I'm leaning towards saying no to this; I think this is out of scope for a PDS and prone to fall out of date over time