From da4932c80b3d7209c1a6607cf632e35789be60b1 Mon Sep 17 00:00:00 2001 From: UMTS at Teleco Date: Sun, 15 Feb 2026 16:08:33 +0100 Subject: Typo --- README.md | 2 ++ overview.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index b2eca14..c2b23c2 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,8 @@ # JsonDerulo API Spec. v2.0 [![JsonDerulo API Spec](https://git.teleco.ch/crt/jsonderulo-api-spec.git/plain/images/jayson-de-json.png)] +> Swallalala + ## What is this? - JsonDerulo Compliant Server Requirements - JsonDerulo (v2) shouldn't be viewed as something only implemented by one backend (even if it is sofar only implemented by one which serves as reference called SeckelAPI) diff --git a/overview.md b/overview.md index 6b01e3e..3cb247c 100644 --- a/overview.md +++ b/overview.md @@ -8,7 +8,7 @@ The server listens on `http://:`. Port is configurable, no specific ## Content Type -Everything is JSON (Derulo bahahahahah). Requests and always responses use `Content-Type: application/json`. +Everything is JSON (Derulo bahahahahah). Requests and all responses use `Content-Type: application/json`. The only exception is when a toolkit endpoint uses `response_format: "passthrough"` for proxying file downloads or something none Jayson from an upstream service. In that case the response mimetype comes from whatever upstream decides to send back. -- cgit v1.2.3-70-g09d2