Hello Sir,
I'm facing a problem with mod_wsgi/lxml configuration. I looked up into
some of the stackoverflow posts and understood that the issue could be with
Library versions.
etree.tostring() removes characters between '<' and '>' on Apache/mod_wsgi
where as the plain Django server works just fine.
*Running standalone Django server (Works Fine)*
{"LXML_VERSION": [4, 2, 1, 0], "*LIBXML_VERSION": [2, 9, 8]*,
"LIBXML_COMPILED_VERSION": [2, 9, 8], "LIBXSLT_VERSION": [1, 1, 32],
"LIBXSLT_COMPILED_VERSION": [1, 1, 32]}
*Running Django over mod_wsgi on Apache*
{"LXML_VERSION": [4, 2, 1, 0], "*LIBXML_VERSION": [2, 9, 1]*,
"LIBXML_COMPILED_VERSION": [2, 9, 8], "LIBXSLT_VERSION": [1, 1, 32],
"LIBXSLT_COMPILED_VERSION": [1, 1, 32]}
I confirmed that the version of LIBXML_VERSION are different between
standalone and mod_wsgi django server.
sfmgr@lelnxweb5014:/data/sfdev/mod_wsgi-4.6.4> ls -lart
/usr/lib64/libxml2.so.2*
-rwxr-xr-x 1 root root 1509408 Jun 6 2016 */usr/lib64/libxml2.so.2.9.1*
lrwxrwxrwx 1 root root 16 Aug 15 2016 /usr/lib64/libxml2.so.2 ->
libxml2.so.2.9.1
*Question?*
How do I get the LIBXML_VERSION updated to 2.9.8? Are you saying that the
system package should be updated? I'm wondering how the LXML_VERSION for
standalone server is picking up 2.9.8 even though the system only contains
2.9.1 version.
Kindly help in this regard. Thanks for your help in advance.
Thanks & regards,
Sujaikumar
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
