Ignacio Piantanida

Hi @denislutz, talkback will store the request body unencoded (human readable) if both the content-type and content-encoding are supported. Most common encodings are supported. What seems to be happening here...

Makes sense, I added a note about it under the [Tapes section](https://github.com/ijpiantanida/talkback#tapes).

I see how this mode can be useful, but I'm doubtful about simply creating multiple tapes that match the same request, since that could easily slip through and lead to...

The problem I see with this approach is: Requests 1 and 2 come, so talkback returns those 2 tapes in the original order. Now comes a 3rd request, because let's...

Currently talkback doesn't support websockets. I'm not sure how it should handle websocket connections, since there's no request/response context that can be used to delimit the different interactions (unless your...

how would talkback know to which host it should proxy to? The way that it's currently recommended is to start 2 different independent talkback servers, but I'm open to suggestions...

Why not as a proxy? The main intent of talkback has been to be used as a "mock" server for integration tests. With that in mind, using talkback as a...

@denislutz that's a great way to setup talkback. What I'm curious about from your example is what setup do you use to point all your different microservice hosts ("your.host.localhost", "your.other.host.localhost")...

I'm not sure I'm understanding the issue. Talkback by default ([code](https://github.com/ijpiantanida/talkback/blob/2f4cf8a693b529498de5b4fbf7a6f035bc15a172/src/request-handler.ts#L137)) already uses `redirect: 'manual'`. I don't see a reason why you would want talkback to follow redirects for you,...

yes if you could post the different HTTP request/responses that would help. Maybe undici is configured to follow redirects automatically? And just to make sure, is this the setup that...