Hi,
Can you provide some nor detail?
- what was your listen path
- what was your target set up to?
If you set up Tyk and followed the tutorials to get an API started, the API will be under /listen-path/resource
The listen path gets stripped out on the outbound request.
The second question I have is, is the 404 being generated by Tyk, or by your upstream service?
The fact that the gateway is blocking/allowing traffic implies the API is being identified and secured, but the outbound request is hitting a 404, which Tyk is just proxying back to you.
This could be because the listen path is stripped out.