Hi Johannes, Thanks for your reply.
In this group, on Mar 19, Milan.M.Masek asked an almost identical question to mine and finally concluded that he had to modify the Python code in mwlib to get it to work. I am trying to find out if he is correct. I've read the readme and there are some things that are not clear; I am sure they are clear once you've done it but they are not obvious if you haven't. In answer to your questions: Yes, HTTP has been disabled on the MediaWiki website in favor of HTTPS. To get at our MediaWiki website, you have to specify https://ourmediawiki. $wgCollectionMWServeURL was not changed to https because the Render Server is NOT behind SSL, just the MediaWiki website. To get to our Render Server you specify http://ourrederserver:8899 Right now I use the mw-serve script to run the Render Server, so Apache is not required and installing a certificate under Apache makes no sense. Do I need to use mwlib.cgi to get it to work and thus use Apache? I really could use a sample setup. On Jul 20, 1:22 am, Johannes Beigel <[email protected]> wrote: > On 19.07.2010, at 21:17, rlfolden wrote: > > > I have mw-serve running on a RedHat Enterprise Server and MediaWiki is > > running on an IIS server. > > > Recently IT decided to enable SSL on the MediaWiki website and now I > > can no longer render pages, but get an error including the string, > > "...could not get collection params...". > > Do you mean that HTTP has been *disabled* in favor of HTTPS? Did you change > http:// to https:// in $wgCollectionMWServeURL? Do you need custom > certificates? See README.txt. > > -- Johannes Beigel -- You received this message because you are subscribed to the Google Groups "mwlib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mwlib?hl=en.
