A hypermodern web server
John Cowan
(18 Sep 2020 00:07 UTC)
|
Re: A hypermodern web server
Arthur A. Gleckler
(18 Sep 2020 01:28 UTC)
|
Re: A hypermodern web server
John Cowan
(18 Sep 2020 02:07 UTC)
|
Re: A hypermodern web server
Arthur A. Gleckler
(18 Sep 2020 03:25 UTC)
|
Re: A hypermodern web server
Amirouche Boubekki
(18 Sep 2020 15:39 UTC)
|
Re: A hypermodern web server
Arthur A. Gleckler
(18 Sep 2020 15:57 UTC)
|
Re: A hypermodern web server Amirouche Boubekki (18 Sep 2020 18:37 UTC)
|
Re: A hypermodern web server
John Cowan
(18 Sep 2020 21:57 UTC)
|
Re: A hypermodern web server
Amirouche Boubekki
(25 Sep 2020 19:56 UTC)
|
Re: A hypermodern web server
Amirouche Boubekki
(18 Sep 2020 15:38 UTC)
|
Re: A hypermodern web server Amirouche Boubekki 18 Sep 2020 18:36 UTC
Le ven. 18 sept. 2020 à 17:57, Arthur A. Gleckler <xxxxxx@speechcode.com> a écrit : > > On Fri, Sep 18, 2020 at 8:39 AM Amirouche Boubekki <xxxxxx@gmail.com> wrote: > >> >> I am not sure what is the point of the current practice to still use >> cookies, outside the fact that cookies are sent implicitly as part of >> every HTTP request. > > > That's an excellent reason by itself, isn't it? I may be wrong about that. I know it is common practice. As far I know HTTP cookies are also a can or jar of worm in the sense they are relatively complex to configure correctly. Again I do not know all-the-things. While writing a pre-srfi, I figured if we support cookies as part of the request, we also need to support them as part of the response, which somewhat complicates things. See https://github.com/pre-srfi/hyperserver#specification