MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Reference_Metadata",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "1396": {
                "pageid": 1396,
                "ns": 0,
                "title": "Recommended Tomcat Setup",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[Category:How_To]]\t\n[[Category:Fusion Registry Install]]\n\n== Recommended Apache Tomcat Setup ==\n\nFusion Registry must be run within a Java Servlet Container. Regnology recommends using Apache Tomcat as the Java Servlet Container, as this has been used during the testing lifecycle of Fusion Registry. The Fusion Registry has only been tested in Apache Tomcat and therefore we cannot guarantee that the Fusion Registry will work with other Java Servlet Containers.\n\nThere are a few things to consider when running Fusion Registry on Apache Tomcat.\n\n=== Security ===\n\nFor enhanced security, we recommend the following:\n\n==== server.xml file ====\n\nBy default, Tomcat will display Stack Traces in certain circumstances.  We recommend the following change be made to the file: '''server.xml'''. This file is located in the Apache Tomcat Directory ''<Apache Root>/conf''\n\nEdit the file and and locate the \"Host\" section.  At the end of this section, just before the closing </Host> tag, insert the following:\n  <Valve className=\"org.apache.catalina.valves.ErrorReportValve\" showReport=\"false\" showServerInfo=\"false\"/>\n\nThis will prevent stack traces from being displayed to the user with HTTP error codes.  Tomcat must be restarted for this change to take effect.\n\n==== context.xml file ====\n\nSince release 11.13 of the Fusion Registry, the product now ships with a default ''context.xml'' file which is located in the META-INF directory in the Fusion Registry directory.  This file overrides Tomcat's cookie pre-processor settings and enforces a strict SameSite cookies policy. More information on SameSite cookie security policies can be found [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie here].  This prevents potential vulnerabilities related to Cross-Site Request Forgery (CSRF).\n\nNo action is required on the deployer's side, but if you want to disable this setting, either change or delete the file."
                    }
                ]
            },
            "529": {
                "pageid": 529,
                "ns": 0,
                "title": "Recover a locked Root User account",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[Category:How_To]]\n= Unlocking a locked Root Account =\n\nTo unlock a locked Root Account in the Registry you will need access to the underlying database that stores all of the Registry information.\n\nIn the database there will be a table with the name 'registry_root_security'.\n\nThis table contains the following information about the root account: the username; the password (encrypted); the number of times a wrong password can be entered before the account is locked; whether or not the root account is locked.\n\nTo unlock a locked root user set the value of the column 'is_locked' to 0. There is no need to restart the Registry after this change, the root user is now unlocked."
                    }
                ]
            }
        }
    }
}