My first XML API integration

November 12, 2010 under Main

While looking into something unrelated, I recently discovered that our anti-spam server software SpamTitan provides an XML API.

I figured I’d have a go at integrating spam filter configuration into the new control panel we’ll be launching soon on www.anu.net. I’m pleased to say it’s done and it took me just a couple hours! Lasso 9’s improved XML type coupled with great documentation from SpamTitan made it a breeze to implement. I’ve added configuration options for various content checks, spam threshold, quarantine digest report frequency and language settings.

Keep an eye out for our new website which we hope to launch within the next month or so.

comments: Closed

Moving your FastCgiIpcDir

November 11, 2010 under Main

The default location for FastCGI to store its sockets on CentOS 5 is /var/log/httpd/fastcgi

The problem here is that you need to open up the permissions on /var/log/httpd from the default 700 to 755 in order for this to work. Should yum decide to update httpd for you, it may reset this, causing a 500 Internal Server Error on your Lasso sites. We learned this the hard way when www.eurolasso.com started doing this one morning.

On my newest L9 server, I’ve moved the FastCGI dir to /var/run/fastcgi

This seems like an appropriate place to put it. You can change it with the apache directive:

FastCgiIpcDir /var/run/fastcgi

NB: make sure you specify the User and Group apache runs under BEFORE this directive. In the default httpd.conf this is specified AFTER the Include conf.d/*.conf directive, and this was causing me to get a permission denied error when trying to start apache. Moving the User and Group directives up above the Include directive fixed this for me.

It’s important to have permissions of 700 on the FastCgiIpcDir as this is where the socket files for connecting to the FastCGI instance live.

I’ve now reset /var/log/httpd to the default 700 and it is working for me.

comments: Closed tags:
Subscribe