hey! i've been reading through the ores and have a few questions and suggestions. here's the first suggestion...
most static file hosts/packages automatically set the content-type header based on the file extension (example: cloudflare workers). the capabilities document at /.well-known/open-ranking doesn't have one, however, which means the developer will have to manually configure the content-type for the file. simply making it /.well-known/open-ranking.json should avoid this step in most cases.
this may seem like a nitpick, but i think it's an easy change that can prevent wasted time troubleshooting.
hey! i've been reading through the ores and have a few questions and suggestions. here's the first suggestion...
most static file hosts/packages automatically set the
content-typeheader based on the file extension (example: cloudflare workers). the capabilities document at/.well-known/open-rankingdoesn't have one, however, which means the developer will have to manually configure thecontent-typefor the file. simply making it/.well-known/open-ranking.jsonshould avoid this step in most cases.this may seem like a nitpick, but i think it's an easy change that can prevent wasted time troubleshooting.