TMS transport defects in the legacy implementation

DEV TMS AI Studio
1

AI analysis of just the TMS.MCP.Transport.StreamableHTTP.pas unit came back with this list:

Disconnect leaves a stale SSE connection pointer
One broken SSE client can kill delivery for everybody
Origin validation is bypassable
Browser bearer auth fails CORS preflight
Several transport errors allow malformed JSON/injection
Wrong missing-version behaviour
Replay storage is unbounded
POST does not appear to enforce the legacy Accept requirements

Any advice?

3

Hi,

Sorry for the delayed answer. Could you specify to us how, when and where these issues are happening? So that we can correctly fix those. We also did a whole lot of improvements in the latest version of the TMS AI Studio. Maybe take a look at the changes to see if this improves the component for you.

With kind regards