@liaizon@social.wake.st I'm testing my split domain setup but it can't seem to resolve your webfinger properly. BrowserPub suggests it's a content-type issue in your webfinger 
6
Replies
0
Boosts
@julian hmm well I'm serving a well-known from github pages and it seemed to work but if you know what I should change lemme know
$ curl -I https://wake.st/.well-known/webfinger?resource=acct:liaizon@wake.st
HTTP/2 200
server: GitHub.com
content-type: application/octet-stream
last-modified: Mon, 24 Aug 2026 11:37:43 GMT
access-control-allow-origin: *
etag: "6a8c2d07-248"
expires: Tue, 25 Aug 2026 20:41:20 GMT
cache-control: max-age=600
x-proxy-cache: MISS
x-github-request-id: 0998:31A41F:B12E62:C2EF36:6A8DFB98
x-github-edge-region: iad
accept-ranges: bytes
age: 0
date: Tue, 25 Aug 2026 20:31:20 GMT
via: 1.1 varnish
x-served-by: cache-yyz4527-YYZ
x-cache: MISS
x-cache-hits: 0
x-timer: S1787689880.196415,VS0,VE190
vary: Accept-Encoding
x-fastly-request-id: be52b8e151d001b8e53e7daa5bbea8c82a4fa06b
content-length: 584
I think it isn't supposed to be application/octet-stream 
@julian looks like it still works ok tho https://webfinger.net/lookup/?resource=liaizon%40wake.st
@liaizon@social.wake.st yeah it does, just seems to be due to stricter checks on my end. I don't know if that's the right content type though.
@julian its because its being served from github pages and theres nothing I can do to change that. cause wake.st is my static website...
