Archive for May, 2009
Squid handling http –> https redirects
Friday, May 29th, 2009In configuring Squid to handle both our port 80 and 443 traffic, we have the issue that we can use redirects at the webserver level to redirect certain pages to https:// . So this is handled in Squid. First, make a simple script. There’s a possibility another redirector like Squirm might do a better job, [...]
Lighttpd, virtual hosts, alternative ports
Friday, May 29th, 2009In the configuration of our new server, all ports 80 and 443 traffic is handled by Squid as a reverse proxy. 8080 is the “backdoor” that bypasses Squid and hits Lighttpd directly. But the standard format of a Lighttpd virtual host entry doesn’t recognize alternate ports appended after the tld. Not a big deal, this [...]
Lighttpd, virtual hosts, and wildcard domains
Friday, May 29th, 2009So we’re setting up mirocommunity.com, and I don’t want to be hassled continously to create new hostnames in DNS. To avoid that, it’s a simple wildcard entry like this in the appropriate named database: *.mirocommunity.com. IN CNAME mirocommunity.com. Which directs everything to our server. Now our server hosts multiple sites via host entries, so we [...]
Adding SSL support to Squid package on Ubuntu
Tuesday, May 26th, 2009Ubuntu doesn’t package OpenSSL support with Squid in their distributions. But you don’t have to quite roll your own and compile from source either! You can add it to the package your self. Verify it doesn’t have ssl support: /usr/sbin/squid3 -v Modify /etc/apt/sources.list adding these lines: deb-src http://us.archive.ubuntu.com/ubuntu jaunty main restricted universe multiverse deb-src http://us.archive.ubuntu.com/ubuntu [...]
Installing Squid to handle both 80 and 443
Tuesday, May 26th, 2009This outlines configuring Squid, running two instances, to handle both port 80 and 443 traffic on an Amazon EC2 instance running Ubuntu Jaunty. We can bypass Squid by going directly to Lighttpd on port 8080. To answer a couple questions off the top, you should also read my post on how to configure http –> [...]