From EDSchminke@Hormel.com Wed Jun 24 08:24:30 2026
From: EDSchminke@Hormel.com
To: xymon@xymon.com
Subject: [Xymon] Chrome cookie deprecations (fix/workaround)
Date: Mon, 18 Jun 2018 15:20:01 -0500
Message-ID:
 <OFD5DAFF1E.B45E74C8-ON862582B0.006D570F-862582B0.006FB267@hormel.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3319427364724848142=="

--===============3319427364724848142==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Hi All,

I wanted to share my fix/workaround for the "Chrome cookie deprecation".

Put the following code above the closing body tag in the
$XYMONHOME/web/stdnormal_footer template file.

-----------------------------------------------------------------------------=
---
<script type=3D"text/javascript">
    var metas =3D document.getElementsByTagName('meta');

    for (var i=3D0; i<metas.length; i++) {
        var type =3D metas[i].getAttribute("HTTP-EQUIV");
        if (type =3D=3D "Set-Cookie") {
            var prop =3D metas[i].getAttribute("CONTENT");
            document.cookie =3D prop;
        }
    }
</script>
-----------------------------------------------------------------------------=
---

Chrome has disabled, as a security measure, the ability to set cookies
using HTML tags.  Xymon (as of v4.3.27) relies on HTML cookies to allow a
user to go from a particular page of monitored hosts to either the
"Acknowledge alert" or "Enable/Disable" pages and, based on the origin,
filter the hosts/alerts for that page.  I've noticed it, as have a few
others in the Xymon community.  This should get us by until a permanent fix
can be implemented in a release version.



Erik D. Schminke | Associate Systems Programmer
Hormel Foods Corporation | One Hormel Place | Austin, MN 55912
Phone: (507) 434-6817
edschminke at hormel.com | www.hormelfoods.com



--===============3319427364724848142==--


From john.thurston@alaska.gov Wed Jun 24 08:24:30 2026
From: john.thurston@alaska.gov
To: xymon@xymon.com
Subject: [Xymon] Chrome cookie deprecations (fix/workaround)
Date: Tue, 19 Jun 2018 11:55:45 -0800
Message-ID: <74b58ca1-d1ed-a681-1c62-f96a2397c7eb@alaska.gov>
In-Reply-To:
 <OFD5DAFF1E.B45E74C8-ON862582B0.006D570F-862582B0.006FB267@hormel.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8086380596251586892=="

--===============8086380596251586892==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

This works well, Erik. Thank you! I offer the following, which I think=20
makes it even better.

Rather than stuffing this directly into the stdnormal_footer template=20
file, go to xymonserver.cfg and adjust the value of XYMONBODYFOOTER.

> XYMONBODYFOOTER=3D"<script type=3D"text/javascript"> var metas =3D document=
.getElementsByTagName('meta'); for (var i=3D0; i<metas.length; i++) { var typ=
e =3D metas[i].getAttribute("HTTP-EQUIV"); if (type =3D=3D "Set-Cookie") { va=
r prop =3D metas[i].getAttribute("CONTENT"); document.cookie =3D prop; } } </=
script>"                                    # HTML inserted at the bottom of =
all webpages.

I already had special stuff in my footer, so I appended (inside the=20
double quotes) the new text to what was already there.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska


--===============8086380596251586892==--


From Paul.Root@CenturyLink.com Wed Jun 24 08:24:30 2026
From: Paul.Root@CenturyLink.com
To: xymon@xymon.com
Subject: [Xymon] Chrome cookie deprecations (fix/workaround)
Date: Tue, 19 Jun 2018 20:46:24 +0000
Message-ID:
 <C88055D0A02F174F848A984067ACC21C750E5E90@podcwmbxex503.ctl.intranet>
In-Reply-To: <74b58ca1-d1ed-a681-1c62-f96a2397c7eb@alaska.gov>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7297574326200816179=="

--===============7297574326200816179==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Being in double quotes. You need to back-slash the double quotes in the line =
don't you?

-----Original Message-----
From: Xymon <xymon-bounces at xymon.com> On Behalf Of John Thurston
Sent: Tuesday, June 19, 2018 2:56 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Chrome cookie deprecations (fix/workaround)

This works well, Erik. Thank you! I offer the following, which I think
makes it even better.

Rather than stuffing this directly into the stdnormal_footer template
file, go to xymonserver.cfg and adjust the value of XYMONBODYFOOTER.

> XYMONBODYFOOTER=3D"<script type=3D"text/javascript"> var metas =3D document=
.getElementsByTagName('meta'); for (var i=3D0; i<metas.length; i++) { var typ=
e =3D metas[i].getAttribute("HTTP-EQUIV"); if (type =3D=3D "Set-Cookie") { va=
r prop =3D metas[i].getAttribute("CONTENT"); document.cookie =3D prop; } } </=
script>"                                    # HTML inserted at the bottom of =
all webpages.

I already had special stuff in my footer, so I appended (inside the
double quotes) the new text to what was already there.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

_______________________________________________
Xymon mailing list
Xymon at xymon.com
http://lists.xymon.com/mailman/listinfo/xymon
This communication is the property of CenturyLink and may contain confidentia=
l or privileged information. Unauthorized use of this communication is strict=
ly prohibited and may be unlawful. If you have received this communication in=
 error, please immediately notify the sender by reply e-mail and destroy all =
copies of the communication and any attachments.

--===============7297574326200816179==--


From john.thurston@alaska.gov Wed Jun 24 08:24:31 2026
From: john.thurston@alaska.gov
To: xymon@xymon.com
Subject: [Xymon] Chrome cookie deprecations (fix/workaround)
Date: Tue, 19 Jun 2018 12:58:37 -0800
Message-ID: <6a54b568-2ed9-925b-87dd-88662e060466@alaska.gov>
In-Reply-To:
 <C88055D0A02F174F848A984067ACC21C750E5E90@podcwmbxex503.ctl.intranet>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2466241609019926639=="

--===============2466241609019926639==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I hadn't even thought of that....but...

On one server I have backslashes, and other I do not. Both seem to=20
arrive in my browser correctly structured with quotes. I have no idea=20
how that happened or why it behaves this way.

Despite my experimental results, escaping those quotes seems prudent.


--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

On 6/19/2018 12:46 PM, Root, Paul T wrote:
> Being in double quotes. You need to back-slash the double quotes in the lin=
e don't you?

--===============2466241609019926639==--


From solitaryr@gmail.com Wed Jun 24 08:24:31 2026
From: solitaryr@gmail.com
To: xymon@xymon.com
Subject: [Xymon] Chrome cookie deprecations (fix/workaround)
Date: Tue, 19 Jun 2018 17:37:44 -0400
Message-ID:
 <CAJpizT2w3ekdp_XyWcHHYqKYDkXTCzODfDgOSPh3EHaqn3GTyg@mail.gmail.com>
In-Reply-To: <6a54b568-2ed9-925b-87dd-88662e060466@alaska.gov>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4179011816974253180=="

--===============4179011816974253180==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

Or just change the embedded double quotes to single quotes...not
backslashes that way.  I'm not aware of anything that would break.

=G=

On Tue, Jun 19, 2018 at 4:58 PM John Thurston <john.thurston at alaska.gov>
wrote:

> I hadn't even thought of that....but...
>
> On one server I have backslashes, and other I do not. Both seem to
> arrive in my browser correctly structured with quotes. I have no idea
> how that happened or why it behaves this way.
>
> Despite my experimental results, escaping those quotes seems prudent.
>
>
> --
>     Do things because you should, not just because you can.
>
> John Thurston    907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
>
> On 6/19/2018 12:46 PM, Root, Paul T wrote:
> > Being in double quotes. You need to back-slash the double quotes in the
> line don't you?
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>

--===============4179011816974253180==--