From 62eb2c53cf465a1a1bd4721528c86b49a0a450fa Mon Sep 17 00:00:00 2001 From: Anton Georgiev Date: Wed, 15 May 2024 10:36:05 -0400 Subject: [PATCH] Update docs/docs/new-features.md --- docs/docs/new-features.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/new-features.md b/docs/docs/new-features.md index af9dd6b961..cff86b07e7 100644 --- a/docs/docs/new-features.md +++ b/docs/docs/new-features.md @@ -198,7 +198,7 @@ In BigBlueButton 2.6.17/2.7.5 we added a new configuration property for bbb-apps #### Removed support for POST requests on `join` endpoint and Content-Type headers are now required -In BigBlueButton 2.6.19/2.7.7 POST requests are no longer allowed for the `join` endpoint. To ensure they are validated properly, a `Content-Type` header must also be provided for POST requests that contain data in the request body. Endpoints now support a limited set of content types that includes `text/xml`, `application/xml`, `application/x-www-form-url-encoded`, and `multipart/form-data`. By default each endpoint only supports `application/x-www-form-urlencoded` and `multipart/form-data`, but individual endpoints can override this and define their own set of supported content types. The `create` endpoint supports all of the four previously listed content types while `insertDocument` supports only `text/xml` and `application/xml`. Any requests with a content type that differs from the set supported by the target endpoint will be rejected with a new `unsupportedContentType` error. +In BigBlueButton 2.6.18/2.7.8 POST requests are no longer allowed for the `join` endpoint. To ensure they are validated properly, a `Content-Type` header must also be provided for POST requests that contain data in the request body. Endpoints now support a limited set of content types that includes `text/xml`, `application/xml`, `application/x-www-form-url-encoded`, and `multipart/form-data`. By default each endpoint only supports `application/x-www-form-urlencoded` and `multipart/form-data`, but individual endpoints can override this and define their own set of supported content types. The `create` endpoint supports all of the four previously listed content types while `insertDocument` supports only `text/xml` and `application/xml`. Any requests with a content type that differs from the set supported by the target endpoint will be rejected with a new `unsupportedContentType` error. ### Development