FoundKey/packages/backend/src
Johann150 624157f03e
server: forbid activitypub requests on unexpected routes
ActivityPub requests on routes which do not support activitypub
are now replying with HTTP status code 406 "Not Acceptable".

ActivityPub clients are required by the W3C TR to set the `Accept`
header. If this accept header is detected on an unexpected route,
the whole request will be aborted with the status code above.

This is an additional measure for clients who might not be aware of
having to check the content-type header of the reply.

Ref: https://github.com/w3c/activitypub/issues/432
Changelog: Security
2024-03-26 21:05:13 +01:00
..
@types use http-signature module that supports hs2019 (#8635) 2022-05-26 09:12:17 +09:00
boot refactor onlyQueue and onlyServer configuration 2023-05-23 19:49:55 +02:00
config BREAKING: activitypub: validate fetch signatures 2023-06-25 20:42:14 +02:00
daemons server: use time constants 2022-11-20 23:15:40 +01:00
db server: remove favorites 2023-05-26 20:59:53 +02:00
mfm server: try to fix link parsing from wafrn.net 2024-01-05 14:15:53 +01:00
misc more compact notifications 2024-03-19 19:09:34 +01:00
models server: remove denormalized note visibility field 2024-01-03 16:13:13 +01:00
prelude server: remove dateUTC function 2023-01-02 12:45:30 +01:00
queue remove unused hashtag chart 2024-03-17 16:48:36 +01:00
remote activitypub: stop accepting collections in inbox 2024-03-20 06:27:01 +01:00
server server: forbid activitypub requests on unexpected routes 2024-03-26 21:05:13 +01:00
services server: only cache public keys for 15min 2024-03-19 19:16:07 +01:00
const.ts backend: minor cleanup of nodeinfo.ts 2022-11-16 17:52:13 -05:00
env.ts Add missing else in log level checking 2023-12-18 05:26:44 +02:00
global.d.ts refactoring 2021-11-12 02:02:25 +09:00
index.ts refactor: remove default export for boot 2022-12-11 14:42:55 -05:00