Looking at the problem, I think that it may have to do with a Zenoss issue and not an apache configuration issue. Wes, it would be great if we could get your howto. Wowever, if possible we would like to do this without altering zope and just proxying through apache. Our apache works on everything except the content on the dashboard and login... When we proxy, we get the dashboard page, but none of the devices show up and 0000-00-00 00:00:00 show up as the last updated date/time. It appears that the dashboard doesn't load any content unless being access directly on port 8080. Do any of the developers have any ideas why this would be occuring?
Thanks, Zakir -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wes Davis Sent: Friday, December 08, 2006 8:47 AM To: General discussion of using zenoss system Subject: Re: [zenoss-users] Apache Proxy Zakir, That's the very same problem I was having, and mod_proxy nor mod_rewrite could really help with. Since my end goal was to use Zenoss with SSL, I ended up going with the Python package M2Crypto (http://wiki.osafoundation.org/bin/view/Projects/MeTooCrypto) to tie in OpenSSL, and that package also has a component (sorry, I'm not well-read on Zope so I don't know the correct terminology) for Zope to give it HTTPS support. I have Apache listening on 80 & 443, and Zope on 8080 & 8443, except 8080 is firewalled off. Apache rewrites the host portion of (most) URLs coming into it to https://***:8443/, and since Zope's still handling the actual session, the URLs in Zenoss & Zope management don't get all mangled. I'm putting together a howto-ish document on my experience getting Zenoss running & configured on an RHEL4 box, I could send you some notes on- or off-list if you like. Wes Durumeric, Zakir B wrote: > Hi, > We have apache proxy working except for two small problems. Wes, you > mentioned that you fixed one of these issues -- but I didn't > understand what you did from your e-mail. > > 1. When I go to http://***/zport, it takes me to the login > /zport/acl_users/... on port 80.. however, once I've successfully > logged in it redirects to port 8080... however, once I'm logged in and > try to manually access a page on port 80, it works fine. > > 2. The dashboard only seems to display with actual information if > access on port 8080, but all the other pages seem to load without any > issues on 80... > > Although we are using 80 right now, we are eventually going to use > this with SSL. > > Thanks, > > Zakir _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
