It came to my attention today that my website was serving blank pages, and I got really intrigued with it. I checked the memory, and everything was fine, and my logs wouldn’t indicate any obvious error. I did a quick research, and some people were saying this happens due to your log files being full which cause your OS’s open file to go nuts, and you run out of file slots.
Continue reading about Apache 101 – Are you rotating your logs?
I have seen people asking this question more than two times now, so I decided it’s about time I write a blog post about it. In ColdFusion it was really easy to solve this problem, as CFIDE is a physical folder, so you could simply move it away from the webroot, and it wouldn’t be accessible to the entire world.
On Railo it’s a bit trickier, as the admin and server folders
are virtual directories, hence you can’t simply “move it away”.
Obviously it’s password protected, so people won’t simply have access
to it and screw up with your configuration, but a more will powered
person could easily brute force into it.
I have to reinforce here that a really will powered lad would
probably break into anything, or even log into your server and make it
a real mess. It’s always good to have this false security sensation
though, so I’ll post here how I do my own security.
Continue reading about CFML 101 – Protecting Railo admin folder
Did you know that search engines consider things like http://www.placona.co.uk/index.cfm and http://placona.co.uk/index.cfm
as duplicate content? It might sound like a wise thing to do, as your
site would be accessible by whichever URL related to your domain. I’ll
say here it’s not, as search engines like Google consider this an
offense and will penalize you should they think you’re doing it on
purpose.
Google normally are very strict and harsh with people trying to “play” with their search engine, or people who try to black hat SEO. And content duplication might be just what will put your domain on the bottom of their search.
I then thought about a very slick way of getting rid of content duplication. You can simply create a rule on your .htaccess (or httpd.conf as that’s what I use), and will will take care of redirecting any request to non-www to a www version of your website.
Continue reading about Apache 101 – Avoiding duplicate content on your domain.
This is only a quick apache tip for when you are using mod_rewrite.
I’ve
been working on some rewriting lately, and noticed that when you use
them, the pattern applied much match exactly, otherwise you will either
get error, or your pattern will never find a match.
Reading time: 2 – 2 minutes This is really for my future reference, but I thought someone would bump into that any time. I’m configuring a new CentOS 5 server and for my surprise it didn’t come with yum installed.
Recent Comments