We had the exact same thing happen on another instance, which basically “broke” dhis2-tools, so for the time being, we are using this specific version of Tomcat as a local install to work around the problem until that instance can be upgraded. Lars suggested this version and it worked for us. Is known to work in this situation for me. On 7 January 2017 at 12:56, Lars Helge Øverland wrote: So getting the exact tomcat versions where the URL checking was introduced will be helpful if you have them. They will have to try and come up with a process of downgrading tomcat and holding that version via the package manager as a short term measure while they plan any dhis2 upgrade process. I can see this is going to cause quite a bit of chaos with large country installations where they are not able to be too agile with upgrading.ĭo you have more precise info on the exact tomcat version numbers? We just saw in Zim (DHIS 2.22) that the package manager automatically upgraded to 7.0.52 and they started seeing these problems. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. Ministry of Health, Nutrition and Indigenous Medicine,Ĭonfidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. MSc (Biomedical Informatics), EMSc (Health Admin) We have patched this now in 2.24, 2.25 and master.īottom line: If you plan to upgrade to very latest Tomcat 7, 8 or 8.5 builds on your server, make sure to upgrade to latest 2.24 or 2.25 of DHIS 2. Our apps had some cases of un-escaped use of the pipe character which was causing tomcat to occasionally return 400 bad request. The latest builds of tomcat (the servlet container mostly used with DHIS 2) has tightened up validation of characters in URLs, so that only characters defined as safe per RFC 1738 are allowed. On Sat, at 6:26 PM, Lars Helge Øverland wrote:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |