posted an update

It would be super cool. If Google Chrome allowed a non-javascript, perhaps header based approach, to store login tokens. That way it would be easier to avoid javascript. It should be like a secondary storage only for authentication and verification. Where the server gave the browser information which the browser automatically added to specific URLs when sending back to the server. But without javascript on the client end. Instead it should be built into the browser and the server should instruct it, like giving it redirect but instead of redirect it is "when you contact these URL points at my server, use these tokens so I know it is you". Again, without the client page needing javascript but the server instructing the browser via the headers or similar. Would be cool. And would let people disable javascript more often to improve security.

Log in or sign up for Devpost to join the conversation.