[FIX] Do not attempt to decode jwt in ws connection is non existing

FrostDigital / fruster-api-gateway

MIT License

0 stars 0 forks source link

[FIX] Do not attempt to decode jwt in ws connection is non existing #73

Closed joelso closed 5 years ago

joelso commented 5 years ago

Avoids these ones (see image) that was due to fact that no JWT was provided when user was logged out, but api gateway still tried to decode the token which caused 400 Bad Request (and which for some reason made client loop and send req again).

joelso commented 5 years ago

retest this please