Timeline for Integrate PHP and WebSocket authentication securely
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2018 at 16:31 | comment | added | Ben Beri | The first part of your answer kinda misunderstands my question for stage two. I never said I will do checks client sided, I said whether if to make it check it on the websocket server, or on the web server. Since most of the logic is handled on the HTTP server, why do it on the websocket server if I only use it as a real-time bridge to my actual application? | |
| Jul 20, 2018 at 14:13 | comment | added | AndrolGenhald | One websocket per user could be problematic for users who like to have multiple tabs open. | |
| Jul 20, 2018 at 14:11 | comment | added | AndrolGenhald | "using a cryptographic hash function [for session id]" - Not a great idea generally, it's not specific enough and not really useful anyway. It's only ok to use a hash for session id if the data being hashed has enough entropy, in which case you might as well just use a CSPRNG directly. | |
| Jul 20, 2018 at 11:39 | history | edited | GxTruth | CC BY-SA 4.0 |
deleted 66 characters in body
|
| Jul 20, 2018 at 11:31 | history | answered | GxTruth | CC BY-SA 4.0 |