Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #31422 > unrolled thread

Logging in without a refresh

Started bybit-naughty@hotmail.com
First post2016-09-21 07:13 -0700
Last post2016-09-24 15:51 +0200
Articles 6 — 3 participants

Back to article view | Back to comp.lang.javascript


Contents

  Logging in without a refresh bit-naughty@hotmail.com - 2016-09-21 07:13 -0700
    Re: Logging in without a refresh "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-09-21 17:37 +0200
    Re: Logging in without a refresh Ram Tobolski <ramtob@gmail.com> - 2016-09-23 02:55 -0700
      Re: Logging in without a refresh "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-09-23 12:02 +0200
        Re: Logging in without a refresh Ram Tobolski <ramtob@gmail.com> - 2016-09-24 06:35 -0700
          Re: Logging in without a refresh "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-09-24 15:51 +0200

#31422 — Logging in without a refresh

Frombit-naughty@hotmail.com
Date2016-09-21 07:13 -0700
SubjectLogging in without a refresh
Message-ID<b530ca25-b997-4661-8f27-4c436c26aec6@googlegroups.com>
I've seen pages, where if you click Login, it pops up a box asking for username+password, if you authenticate, it *logs you in without a refresh*!!, ie.  the box says "Authenticated" or whatever, and disappears, and the page behind is now logged in. I'm interested in the mechanics of this, but what I'd like most of all to know is - is the cookie that's set on the client side set on the server side or the client, ie. in PHP or Javascript?

Thanks.

[toc] | [next] | [standalone]


#31423

From"Evertjan." <exxjxw.hannivoort@inter.nl.net>
Date2016-09-21 17:37 +0200
Message-ID<XnsA68AB34E6D406eejj99@194.109.6.166>
In reply to#31422
bit-naughty@hotmail.com wrote on 21 Sep 2016 in comp.lang.javascript:

> I've seen pages, where if you click Login, it pops up a box asking for
> username+password, if you authenticate, it *logs you in without a
> refresh*!!, ie.  the box says "Authenticated" or whatever, and
> disappears, and the page behind is now logged in.

You are just assuming.
Better do some reseach on the page, 
try F12 and inspect the clientside code.

> I'm interested in the
> mechanics of this, but what I'd like most of all to know is - is the
> cookie that's set on the client side set on the server side or the
> client

You are just assuming.

Cookies are always clientside.

Cookies, therefore are unsafe for authentication.

Serverside session-variables are much safer.

> ie. in PHP or Javascript? 

You are just assuming.

Serverside can have a bunch of other languages than PHP,
even including Javascript.


-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]


#31434

FromRam Tobolski <ramtob@gmail.com>
Date2016-09-23 02:55 -0700
Message-ID<06bd0f6d-0b3b-4d40-aced-74545136c065@googlegroups.com>
In reply to#31422
On Wednesday, September 21, 2016 at 5:14:34 PM UTC+3, bit-n...@hotmail.com wrote:
> I've seen pages, where if you click Login, it pops up a box asking for username+password, if you authenticate, it *logs you in without a refresh*!!, ie.  the box says "Authenticated" or whatever, and disappears, and the page behind is now logged in. I'm interested in the mechanics of this

This would be done by Ajax, i.e. asynchronous client-server communication, using javascript. Today this would usually be done through a javascript SPA (single page application) framework, such as angular.js or react.js.

[toc] | [prev] | [next] | [standalone]


#31435

From"Evertjan." <exxjxw.hannivoort@inter.nl.net>
Date2016-09-23 12:02 +0200
Message-ID<XnsA68C7A881D7Ceejj99@194.109.6.166>
In reply to#31434
Ram Tobolski <ramtob@gmail.com> wrote on 23 Sep 2016 in
comp.lang.javascript: 

> On Wednesday, September 21, 2016 at 5:14:34 PM UTC+3,
> bit-n...@hotmail.com wrote: 
>> I've seen pages, where if you click Login, it pops up a box asking for
>> us 
> ername+password, if you authenticate, it *logs you in without a
> refresh*!!, ie.  the box says "Authenticated" or whatever, and
> disappears, and the page behind is now logged in. I'm interested in the
> mechanics of this 
> 
> This would be done by Ajax, i.e. asynchronous client-server
> communication, using javascript. Today this would usually be done
> through a javascript SPA (single page application) framework, such as
> angular.js or react.js. 

How could you know, as today usually is not finished yet?

In stricter sense, today never can be finished in the present.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]


#31440

FromRam Tobolski <ramtob@gmail.com>
Date2016-09-24 06:35 -0700
Message-ID<57288191-cc28-4269-9f1e-ea85ca88311a@googlegroups.com>
In reply to#31435
>How could you know, as today usually is not finished yet? 
In stricter sense, today never can be finished in the present.

Perhaps we should move this topic to the philosophy group?

[toc] | [prev] | [next] | [standalone]


#31441

From"Evertjan." <exxjxw.hannivoort@inter.nl.net>
Date2016-09-24 15:51 +0200
Message-ID<XnsA68DA142E7B79eejj99@194.109.6.166>
In reply to#31440
Ram Tobolski <ramtob@gmail.com> wrote on 24 Sep 2016 in comp.lang.javascript:

>> How could you know, as today usually is not finished yet? 
>> In stricter sense, today never can be finished in the present.
> 
> Perhaps we should move this topic to the philosophy group?

When? 

Tomorrow?


-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.javascript


csiph-web