I m having trouble with NestJS + GraphQL I ve seen there wer

Question

I m having trouble with NestJS + GraphQL I ve seen there were older messages about this in discord but it didn t really help Honestly I have no clue of how according to the supertokens documentation of vanilla graphql on nodejs this should be done ```ts Injectable export class GQLAuthGuard implements CanActivate async canActivate context ExecutionContext Promise<boolean> const ctx = GqlExecutionContext create context getContext let err = undefined You can create an optional version of this by passing sessionRequired false to verifySession await verifySession sessionRequired false ctx req ctx res res => err = res if ctx res headersSent throw new STError message RESPONSE SENT type RESPONSE SENT if err throw err return true ```

rp · Answer

What s the error you are facing

FrAgOrDiE · Answer

There are many in different scenarios here s the one I get by calling a graphql endpoint being unauthenticated ``` D git evt server node modules supertokens node lib build framework express framework js 36 step generator throw value ^ TypeError next is not a function at D git evt server node modules supertokens node lib build framework express framework js 179 24 at Generator throw <anonymous> at rejected D git evt server node modules supertokens node lib build framework express framework js 36 44 at processTicksAndRejections node internal process task queues 96 5 ```

FrAgOrDiE · Answer

The response looks correct but it makes the server crash

rp · Answer

Do you know which function in your code causes this

FrAgOrDiE · Answer

I had to wait the session to expire because it s the only scenario that causes the error

FrAgOrDiE · Answer

The error happens into the code I sent above

FrAgOrDiE · Answer

ctx res headersSent seems to be true

rp · Answer

You can delete the sAccessToken in the cookie and then it would be like as if it s expired

rp · Answer

I see So which error handler is catching that error

rp · Answer

The one that s thrown in that if block

FrAgOrDiE · Answer

Alright I m starting to understand The error is handled by this ```ts Catch STError export class SupertokensExceptionFilter implements ExceptionFilter handler ErrorRequestHandler constructor this handler = errorHandler catch exception Error host ArgumentsHost const ctx = host switchToHttp const resp = ctx getResponse if resp headersSent return this handler exception ctx getRequest resp ctx getNext ```

FrAgOrDiE · Answer

which I just figured out it s not meant to handle graphql context

FrAgOrDiE · Answer

correct

rp · Answer

Yea Correct

FrAgOrDiE · Answer

So I m trying to do something like this

FrAgOrDiE · Answer

```ts if ctx res headersSent throw new GQLSTError message RESPONSE SENT type RESPONSE SENT ```

FrAgOrDiE · Answer

I m throwing a different exception

FrAgOrDiE · Answer

GQLSTError extends STError

rp · Answer

You can As long as In that handler you check that the type is response sent and just return

rp · Answer

Cause if you send a response again it will throw a different error

FrAgOrDiE · Answer

ok that doesn t seem to work

FrAgOrDiE · Answer

```ts Catch STError export class SupertokensExceptionFilter implements ExceptionFilter handler ErrorRequestHandler constructor this handler = errorHandler catch exception Error host ArgumentsHost if exception instanceof GQLSTError return added this const ctx = host switchToHttp const resp = ctx getResponse if resp headersSent return this handler exception ctx getRequest resp ctx getNext ```

FrAgOrDiE · Answer

now the exception isn t caught by this filter

FrAgOrDiE · Answer

neither by the other one though

FrAgOrDiE · Answer

oh wait

FrAgOrDiE · Answer

didn t register it on main ts

FrAgOrDiE · Answer

okay so

FrAgOrDiE · Answer

how do I get the ExecutionContext from here `catch exception Error host ArgumentsHost `

FrAgOrDiE · Answer

I used to access the GQL request by hardcoding the arg index like this ```ts ctx getArgByIndex 2 ```

FrAgOrDiE · Answer

by the way the filter works and ```ts catch exception Error host ArgumentsHost const context = host getArgByIndex 2 if context res headersSent return this handler exception context req context res context next ``` context res headersSent is set to true so I get the correct response back to the client but in the server console I get this error ``` Error Cannot set headers after they are sent to the client at new NodeError node internal errors 371 5 at ServerResponse setHeader node http outgoing 573 11 at D git evt server node modules apollo server express src ApolloServer ts 171 19 at processTicksAndRejections node internal process task queues 96 5 ```

rp · Answer

Yea in your erorr handler you need to check if the err has `type == RESPONSE SENT ` and if that s true then you just return from the error handler

FrAgOrDiE · Answer

```ts catch exception Error host ArgumentsHost if exception message === RESPONSE SENT return const context = host getArgByIndex 2 if context res headersSent return this handler exception context req context res context next ```

FrAgOrDiE · Answer

now it s done and it s still throwing the error

FrAgOrDiE · Answer

by debugging it I can see it enters into the if statement and return

FrAgOrDiE · Answer

but still ``` Error Cannot set headers after they are sent to the client at new NodeError node internal errors 371 5 at ServerResponse setHeader node http outgoing 573 11 at D git evt server node modules apollo server express src ApolloServer ts 171 19 at processTicksAndRejections node internal process task queues 96 5 ```

rp · Answer

Hmmm I m not too sure at the moment Can you open an issue about this on o ur GitHub and we can suggest a solution that will work tomorrow or day after

FrAgOrDiE · Answer

I was going to then I noticed it works with `antiCsrfCheck false` do you have any idea of why Otherwise I m ok with github issue

rp · Answer

Right So when you query the API you must not be setting a rid header

rp · Answer

How r you querying it

rp · Answer

Using postman Or fetch axios

FrAgOrDiE · Answer

postman I do not set the rid

rp · Answer

So you should set rid If you are querying your own api set the value of it to rid anti csrf