Bug #64539 [Opn]: FPM status page: query_string not properly JSON encoded
Edit report at https://bugs.php.net/bug.php?id=64539&edit=1
ID: 64539
Updated by: cmb@php.net
Reported by: benpro at benpro dot fr
-Summary: FPM status page: JSON parse error
+Summary: FPM status page: query_string not properly JSON
encoded
Status: Open
Type: Bug
Package: FPM related
Operating System: Debian 6.0.6
-PHP Version: 5.3.23
+PHP Version: 7.4
Block user comment: N
Private report: N
New Comment:
Appears to be still unresolved.
Previous Comments:
------------------------------------------------------------------------
[2021-08-23 18:15:53] cmb@php.net
Related To: Bug #66119
------------------------------------------------------------------------
[2021-05-31 14:41:35] chris at kruining dot eu
laruence@php.net Here is a blogpost regarding this issue; https://thomasp.vivaldi.net/2021/04/01/a-noisy-check/.
The author of the post initially tried to work this out by encoding as well, but to no avail. And
whichever piece of code that encodes to JSON -where-ever it may be- should -imo- be responsible for
for properly encoding the contents.
------------------------------------------------------------------------
[2021-05-29 11:26:10] michiel at hazelhof dot nl
#66119 seems to be a duplicate but with a clearer description.
Because the output of status?json isn't properly encoded all kinds of status monitoring tools
break when encountering unescaped characters.
------------------------------------------------------------------------
[2014-12-15 09:11:06] terry dot lee dot core at gmail dot com
Hi, could you explain what is the element "last request cpu": 0.00 unit. i have the data
with the last request cpu:234, means use the cpu 234%?
------------------------------------------------------------------------
[2013-03-31 11:58:25] laruence@php.net
as the html says, "This is sample real-time status page for FPM. You can change it
to better feet your needs."
maybe you need escape the backslash in request uri by yourself
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=64539
--
Edit this bug report at https://bugs.php.net/bug.php?id=64539&edit=1
Thread (7 messages)