Message from JavaScript discussions

November 2020

— But it's doable (never did that)

— 

Today cookies are set automatically by some server-side code, all the work left to the coder is to check session value to determine who is the user

— But what you are saying the best thing to do is make the login on its own server and the information etc from the rest api

Message permanent page

— Thats the only possible way I see it now

— Best way, magic wand, i don't get what you mean

— Bruh anyone still using webpack?

— Pebpack wat pack🤔

— Not gonna lie but there's worse than webpack, imagine still using parcel f.e.

— I have the same cases previously, I store my token generated by jsonwebtoken on cookie on route /api/v1/jwt when I started to move another route /api/v1/product protected by express-jwt I got response status 401.

Message permanent page

— It means that the cookies is missing, so I setup the server specifically I made a changes cors() to cors({ credentials: true }) and for the client I use axios for fetching the data, I add option axios.defaults.credentials = true`

Message permanent page

— And it's fix the problem 😂

— Yeah a "social network" where you can't even ignore abusive people in groupchats and where the 1-to-1 messaging doesn't even use E2EE by default.

Message permanent page