21.8.08
Custom 404 pages - Webmaster Help Center
Custom 404 pages
A 404 page is what a user sees when they try to reach a non-existent page on your site (because they've clicked on a broken link, the page has been deleted, or they've mistyped a URL). A 404 page is called that because in response to a request for a missing page, webservers send back a HTTP status code of 404 to indicate that a page is not found. While the standard 404 page can vary depending on your ISP, it usually doesn't provide the user with any useful information, and most users may just surf away from your site.
If you have access to your server, we recommend that you create a custom 404 page. A good custom 404 page will help people find the information they're looking for, as well as providing other helpful content and encouraging them to explore your site further.
(Note: This article covers guidelines for creating the content of your custom 404 page. For information on configuring your server to display your new 404 page, check your server or web hoster documentation. You should still make sure that your webserver returns a 404 status code to users and spiders, so that search engines don't accidentally index your custom 404 page.)
Because a 404 page can also be a standard HTML page, you can customize it any way you want. Here are some suggestions for creating an effective 404 page that can help keep visitors on your site and help them find the information they're looking for:
- Tell visitors clearly that the page they're looking for can't be found. Use language that is friendly and inviting.
- Make sure your 404 page uses the same look and feel (including navigation) as the rest of your site.
- Consider adding links to your most popular articles or posts, as well as a link to your site's home page.
- Think about providing a way for users to report a broken link.
- No matter how beautiful and useful your custom 404 page, you probably don't want it to appear in Google search results. In order to prevent 404 pages from being indexed by Google and other search engines, make sure that your webserver returns an actual 404 HTTP status code when a missing page is requested.
20.8.08
.htaccess Plugin Blocks Spam, Hackers, and Password Protects
read more | digg story
Crazy Advanced Mod_Rewrite Tutorial
read more | digg story
19.8.08
18.8.08
WP Plugin: all-in-one htaccess plugin
read more | digg story
AdesBlog.com » WP Plugin: all-in-one htaccess plugin
With .htaccess you can do so many things, but the risky part is almost all the time you need to edit your .htaccess file manually. However, now there is a special htaccess wp plugin for wordpress blogs that does so many things (full features are below the screenshot). All you need is “enable” a particular feature and it will rewrite your .htaccess file automatically.
Full Features
- Directory Protection
Enable the DirectoryIndex Protection, preventing directory index listings and defaulting. - Password Protect wp-login.php
Requires a valid user/pass to access the login page - Password Protect wp-admin
Requires a valid user/pass to access any non-static (css, js, images) file in this directory. - Protect wp-content
Denies any Direct request for files ending in .php with a 403 Forbidden. - Protect wp-includes
Denies any Direct request for files ending in .php with a 403 Forbidden. - Common Exploits
Block common exploit requests with 403 Forbidden. - Stop Hotlinking
Denies any request for static files (images, css, etc) if referrer is not local site or empty. - Safe Request Methods
Denies any request not using GET,PROPFIND,POST,OPTIONS,PUT,HEAD - Forbid Proxies
Denies any POST Request using a Proxy Server. Can still access site, but not comment. See Perishable Press - Real wp-comments-post.php
Denies any POST attempt made to a non-existing wp-comments-post.php - HTTP PROTOCOL
Denies any badly formed HTTP PROTOCOL in the request, 0.9, 1.0, and 1.1 only - SPECIFY CHARACTERS
Denies any request for a url containing characters other than “a-zA-Z0-9.+/-?=&” - REALLY helps but may break your site depending on your links. - BAD Content Length
Denies any POST request that doesnt have a Content-Length Header - BAD Content Type
Denies any POST request with a content type other than application/x-www-form-urlencoded|multipart/form-data - Directory Traversal
Denies Requests containing ../ or ./. which is a directory traversal exploit attempt - PHPSESSID Cookie
Only blocks when a PHPSESSID cookie is sent by the user and it contains characters other than 0-9a-z - *** Safe, Use - NO HOST:
Denies requests that dont contain a HTTP HOST Header. - Bogus Graphics Exploit
Denies obvious exploit using bogus graphics - No UserAgent, No Post
Denies POST requests by blank user-agents. May prevent a small number of visitors from POSTING. - No Referer, No Comment
Denies any comment attempt with a blank HTTP_REFERER field, highly indicative of spam. - Trackback Spam
Denies obvious trackback spam. See Holy Shmoly! - SSL-Only Site
Redirects all non-SSL (https) requests to your https-enabled url - Anti-Spam, Anti-Exploits
Denies Obvious Spam and uses advanced mod_security protection
Go get it tiger! ;)
Plugin page: www.askapache.com/wordpress/htaccess-password-protect.html
Max Design - standards based web design, development and training » Some links for light reading (12/8/08)
Some links for light reading (12/8/08)
August 12th, 2008
- Deafness and the User Experience
- Putting Our Hot Heads Together
- PingMyMap
- Facelife v1.1
- Startup, Inc - What You Need to Know Before Starting a Company
- 5 Useful Coding Solutions For Designers and Developers
- MapIconMaker
- Design for Emotion and Flow
- Designing the online newsroom
- Galleries: The Hardest Working Pages on Your Site
- It’s 404 week at Webmaster Central
- Specifics on CSS Specificity
- Borderline semantics
- End of Life for PHP 4
- Htaccess SEO Trends by Google
In Praise of Minify
read more | digg story
11.8.08
AskApache is pushing mod_rewrite boundaries to the limits
read more | digg story
9.8.08
Elite Log File Scrolling with Color Syntax
read more | digg story