Re: Request regarding inputs

[Jim Breen <jimbreen@*********>]

Very interesting discussion on cookies. I hadn't realised that the
wwwjdic cookie is available to the whole domain.

The wwwjdic cookie itself is rather out-of-date. The name and email
address is no longer used since the old new-entry/edit feature was
replaced back in 2010 with a link to jmdictdb, and all the options for
disabling the links are no longer relevant since I replaced them with
the drop-down [Links] menu some years back. I won't fiddle with it
now, and the name/address parts certainly could be picked up by the
jmdictdb code if that's useful.

The cookie is set by the page at:
https://www.edrdg.org/cgi-bin/wwwjdic/wwwjdic?19B

Jim

On Sat, 2 Mar 2024 at 05:18, Stuart McGraw <jmdictdb@mtneva.com> wrote:
>
> [Sorry about the previous premature send]
>
> Very helpful information, thank you.
>
> If the wwwjdic cookie is already set when a jmdictdb page is generated, I think the jmdictdb page can extract the name and email address easily enough.  Going the other way -- a user filling out a jmdictdb form's name and email when no wwwjdict cookie is set -- would ideally set the same cookie.  That will allow the entered name/address to be propagated to the wwwjdict pages.  But I'll need input from Jim regarding what is needed or not needed regarding the other fields in the cookie and it will also require future coordination should the format change.  Alternatively, there could be a second jmdictdb-only cookie used when a wwwjdic cookie is not available but this would mean no propagation to wwwjdic pages.
>
> -- Stuart
>
>
> On 2/29/24 22:52, Ben Bullock wrote:
> > On Fri, 1 Mar 2024 at 02:31, Stuart McGraw <smcg6347@*********** <mailto:smcg6347@***********>> wrote:
> >     I'm not sure how hard it will be to share cookies between Jim's wwwjdic pages and the jmdictdb pages.
> >
> > The WWWJDIC cookie code sets the path to the top level using path=/, so the cookie is already useable across the whole of the edrdg.org <http://edrdg.org> domain. The dictionary database server is receiving the cookie with each web request. The following screenshot shows the display of the "Dev Tools" in the Chrome web browser for the top page of the dictionary server, https://www.edrdg.org/jmwsgi/edform.py?svc=jmdict&c=1 <https://www.edrdg.org/jmwsgi/edform.py?svc=jmdict&c=1>. Here I have highlighted where the cookie with the key wwwjdicparm was sent with the request:
> >
> > [image: wwjdicparm.png]
>
> --
> You received this message because you are subscribed to the Google Groups "EDICT-JMdict" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to edict-jmdict+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/edict-jmdict/0c75ceaa-e961-4136-bdec-e166aabb0bb9%40mtneva.com.



-- 
Jim Breen
Adjunct Snr Research Fellow, Japanese Studies Centre, Monash University
http://www.jimbreen.org/
http://nihongo.monash.edu/

-- 
You received this message because you are subscribed to the Google Groups "EDICT-JMdict" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edict-jmdict+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edict-jmdict/CABHGxq4sNESbQ2z_VD6fASCL5CMMc30bDU53vL9aLmvtiE%2B8sA%40mail.gmail.com.