Earlier quoted context omitted.
They are not really, really essential. No cookie is essential. A long, long time ago I worked with a web system that kept session info in a URL parameter, and carried it over all the links. I think it was a C# website, but I'm not sure.
>a URL parameter I love those systems. Especially when the unwary users share links, accidentally letting other users into the site as them. Or when google indexes it, and in addition to terrible security, the site uses regular GET links to perform site actions, so google deletes the user's content or buys a bunch of stuff as them while walking the links it finds as it indexes in beyond the user's initial account bea…
No Cookie for You
631–634 of 634 posts
Re: No Cookie for You
#632Earlier quoted context omitted.
They are not really, really essential. No cookie is essential. A long, long time ago I worked with a web system that kept session info in a URL parameter, and carried it over all the links. I think it was a C# website, but I'm not sure.
Those were great. I hung around a forum around 2004 where someone posted a link to jeans he just bought from a smallish online store - the URL contained the PHP session identifier. Thousands of people had instant access to his address + bank information + purchase history, and could place orders for him.
Re: No Cookie for You
#633Earlier quoted context omitted.
Would this mean that if you shared a URL with someone you would be sharing your session as well?
Yes. Some sites operating like that eventually tried to work around this issue by tying it to the IP, but you can see how that is hopelessly broken anyway.
Re: No Cookie for You
#634Earlier quoted context omitted.
They are not really, really essential. No cookie is essential. A long, long time ago I worked with a web system that kept session info in a URL parameter, and carried it over all the links. I think it was a C# website, but I'm not sure.
That would break the "remember me" feature for sure, unless you explicitly bookmark the site with the get parameter attached. It also poses a security / opsec issue if anyone non-technical wants to send a link to a friend / co-worker. You may compromise yourself. If people share their screen people would be able to hijack the session too. You won't be able to distinguish device sessions from one another reliably neit…
You could, I think. Passing the session ID in the URL is the same as storing it as a cookie. You can invalidate both in the server.
Link sharing is an issue, for sure. You could tie the session id to the IP, but that doesn't work when people share their IP, which is more and more common every day. IP tied session would work better with IPv6, though.