refactor: 📝 Use new Versia content-type everywhere
Some checks failed
Mirror to Codeberg / Mirror (push) Failing after 0s

This commit is contained in:
Jesse Wierzbinski 2025-05-13 15:31:35 +02:00
parent e138e9e7c3
commit c6c5945bef
No known key found for this signature in database
3 changed files with 8 additions and 8 deletions

View file

@ -37,7 +37,7 @@ export const metadata = {
```http {{ 'title': 'Example response' }}
HTTP/1.1 200 OK
Content-Type: application/vnd.versia+json
Content-Type: application/vnd.versia+json; charset=utf-8
{
"type": "InstanceMetadata",
@ -81,7 +81,7 @@ export const metadata = {
```http {{ 'title': 'Example response' }}
HTTP/1.1 200 OK
Content-Type: application/vnd.versia+json
Content-Type: application/vnd.versia+json; charset=utf-8
{
"type": "User",
@ -125,7 +125,7 @@ export const metadata = {
```http {{ 'title': 'Example response' }}
HTTP/1.1 200 OK
Content-Type: application/vnd.versia+json
Content-Type: application/vnd.versia+json; charset=utf-8
{
"type": "Followers",
@ -173,7 +173,7 @@ The delivery mechanism is described further in the [Federation](/federation) doc
POST /.versia/v0.6/inbox
Host: b.social
Accept: application/vnd.versia+json
Content-Type: application/vnd.versia+json
Content-Type: application/vnd.versia+json; charset=utf-8
{
"type": "Note",