So, TYK expects the the POST Content-Type to be 'application/x-www-form-urlencoded' and redirects to the applications Login/Authorization page.
Now the way we have it working is that the user credentials are provided during that first call to tyk for client authorization. which means. the user credentials are part of the POST body in the redirect to the authorization page. The credentials are then validated.
So, the use case we are trying to achieve is to have the Content-Type header to be "application/vnd.api+json" and be strictly JSONApi in our responses. This is not currently possible since the header needs to be 'application/x-www-form-urlencoded'.
So I wanted to see if that header could be changed during the 304 redirect to the authorization page in TYK, similar to header transformation during Proxying. This would allow us to inject/change that header and be JsonApi compliant.