Web Design and Development


  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/swaratec/public_html/modules/views/handlers/views_handler_argument.inc on line 0.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/swaratec/public_html/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/swaratec/public_html/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter_node_status::operator_form() should be compatible with views_handler_filter::operator_form(&$form, &$form_state) in /home/swaratec/public_html/modules/views/modules/node/views_handler_filter_node_status.inc on line 0.
  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home/swaratec/public_html/modules/views/plugins/views_plugin_style_default.inc on line 0.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/swaratec/public_html/modules/views/plugins/views_plugin_row.inc on line 0.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/swaratec/public_html/modules/views/plugins/views_plugin_row.inc on line 0.
  • strict warning: Non-static method view::load() should not be called statically in /home/swaratec/public_html/modules/views/views.module on line 879.

This seems to be what people think htaccess was meant for, but it is only part of the general use. We’ll be getting into progressively more advanced stuff after this.

In order to specify your own ErrorDocuments, you need to be slightly familiar with the server returned error codes. (List to the right). You do not need to specify error pages for all of these, in fact you shouldn’t. An ErrorDocument for code 200 would cause an infinite loop, whenever a page was found…this would not be good.

Ever wanted a specific directory in your site to be available only to people who you want it to be available to? Ever got frustrated with the seeming holes in client-side options for this that allowed virtually anyone with enough skill to mess around in your source to get in? htaccess is the answer!

Is there a pesky person perpetrating pain upon you? Stalking your site from the vastness of the electron void? Blockem! In your htaccess file, add the following code–changing the IPs to suit your needs–each command on one line each:

Ever go through the nightmare of changing significantly portions of your site, then having to deal with the problem of people finding their way from the old pages to the new? It can be nasty. There are different ways of redirecting pages, through http-equiv, javascript or any of the server-side languages. And then you can do it through htaccess, which is probably the most effective, considering the minimal amount of work required to do it.

Syndicate content Web Design and Development


Back to top