Émile Fugulin

@mattsse Lets close that issue, no point in keeping that here

We don't currently have anything in terms of UI interactions with workflows, this is a big undertaking. Our current suggestions will be to use backend + frontend plugins for a...

Looks like it might be related to socket.io ``` 2024-01-01T12:22:41.513279Z INFO main ResponseSender: GET https://tryhackme.com/socket.io/?EIO=4&transport=websocket -> 101 714 (2d24e818-c16d-4cc1-8d53-ff4467c91176) 2024-01-01T12:22:41.516719Z INFO main WSHandler: Switching to Websocket (2d24e818-c16d-4cc1-8d53-ff4467c91176) 2024-01-01T12:22:41.522545Z ERROR main...

For the next version of Caido we will start stripping the extension header automatically which will some the problem. If you need this header, please let us know and we...

The current work-around is to add a match and replace rule that will strip the `Sec-WebSocket-Extensions` header

### What to test `Per-Message Compressed` is properly stripped Client (Python) -> Caido -> Server (Python) Client needs to request websocket per message compression (header) https://datatracker.ietf.org/doc/html/rfc7692 Try to toggle the...

I am not sure I want to introduce that, the missing rule is due to a missing subscription which we need to deal with anyway for multi-user mode.

This is essentially the active workflow system that is coming soon

Trying to understand in which context exactly? Is it during renders or is it like a tamper rule that injects it on next requests?

My initial thought is that goal is to have a proper DSL so you don't have to know the structure of a json schema to build one, this doesn't really...