Now for today's question: Has anyone ever figured out how to configure Zonealarm Pro to be able to stay logged into a XOOPS installation on localhost? We supposedly use the local installation to test the stuff we're not so sure about, and it would be nice to not always have to bring the firewall down while doing that.

Edit: I think I found a solution myself. Replacing 127.0.0.1 for localhost in the XOOPS URL (in mainfile.php), and then defining an entry in ZoneAlarm privacy settings allowing cookies and headers from 127.0.0.1 seems to be doing the job. ZoneAlarm privacy settings wouldn't accept an entry for "localhost", which comes with the XOOPS URL if not changed in the XOOPS settings.

Check the first comment in this faq.

Rowd

(after your edit) It would be appreciated if you could add your findings to the faq comments

Hehehe, that was a little premature it seems. That trick made perfect sense to me, unfortunately that darn ZoneAlarm is still blocking cookies. Which is probably because they come from Apache and the PHP engine, so there might be something to be set in their configuration files.

In any case, once the cookie is set, my tweak lets me bring up the firewall again and navigate my local XOOPS site ... until the cookie expires, that is. Perhaps, someone can take it from here if there's interest...

But, with a computer connected on a stable IP (for instance through a router; such an IP would typically start with 192...), it seems to work if the computer's IP is entered as the XOOPS URL and then exempted from cookie control in Zonealarm Privacy. Instead of "localhost", again. It's a little wacky, though, with the router having to reflect back your requests to your own machine. Also means you can't view your site if you're not connected to the router. But I've browsed the forums at ZoneLabs, and that seems to be the only solution people have come up with.

Don't think this is a prime time solution worthy of going into FAQs?