Difference between revisions of "Rewrite engine"

From Christoph's Personal Wiki
Jump to: navigation, search
(→‎mod_rewrite)
(→‎mod_rewrite)
Line 12: Line 12:
 
== mod_rewrite ==
 
== mod_rewrite ==
  
−
<div style="float:left; margin:0px 20px 20px 0px;">
+
<div style="float:left; margin:0px 0px 0px 0px;">
 
{| align="center" style="border: 1px solid #999; background-color:#FFFFFF"
 
{| align="center" style="border: 1px solid #999; background-color:#FFFFFF"
 
|-
 
|-
Line 51: Line 51:
 
|}
 
|}
 
</div>
 
</div>
 +
 +
=== Server Variables ===
 +
==== Format ====
 +
* <tt>%{NAME_OF_VAR}</tt>
 +
==== HTTP Headers ====
 +
* <tt>HTTP_USER_AGENT</tt>
 +
* <tt>HTTP_REFERER</tt>
 +
* <tt>HTTP_COOKIE</tt>
 +
* <tt>HTTP_FORWARDED</tt>
 +
* <tt>HTTP_HOST</tt>
 +
* <tt>HTTP_PROXY_CONNECTION</tt>
 +
* <tt>HTTP_ACCEPT</tt>
 +
==== Request ====
 +
* <tt>REMOTE_ADDR</tt>
 +
* <tt>REMOTE_HOST</tt>
 +
* <tt>REMOTE_USER</tt>
 +
* <tt>REMOTE_IDENT</tt>
 +
* <tt>REQUEST_METHOD</tt>
 +
* <tt>SCRIPT_FILENAME</tt>
 +
* <tt>PATH_INFO</tt>
 +
* <tt>QUERY_STRING</tt>
 +
* <tt>AUTH_TYPE</tt>
 +
==== Server ====
 +
* <tt>DOCUMENT_ROOT</tt>
 +
* <tt>SERVER_ADMIN</tt>
 +
* <tt>SERVER_NAME</tt>
 +
* <tt>SERVER_ADDR</tt>
 +
* <tt>SERVER_PORT</tt>
 +
* <tt>SERVER_PROTOCOL</tt>
 +
* <tt>SERVER_SOFTWARE</tt>
 +
==== Time ====
 +
* <tt>TIME_YEAR</tt>
 +
* <tt>TIME_MON</tt>
 +
* <tt>TIME_DAY</tt>
 +
* <tt>TIME_HOUR</tt>
 +
* <tt>TIME_MIN</tt>
 +
* <tt>TIME_SEC</tt>
 +
* <tt>TIME_WDAY</tt>
 +
* <tt>TIME</tt>
 +
==== Special ====
 +
* <tt>API_VERSION</tt>
 +
* <tt>THE_REQUEST</tt>
 +
* <tt>REQUEST_URI</tt>
 +
* <tt>REQUEST_FILENAME</tt>
 +
* <tt>IS_SUBREQ</tt>
 +
==== Directives ====
 +
* <tt>RewriteEngine</tt>
 +
* <tt>RewriteOptions</tt>
 +
* <tt>RewriteLog</tt>
 +
* <tt>RewriteLogLevel</tt>
 +
* <tt>RewriteLock</tt>
 +
* <tt>RewriteMap</tt>
 +
* <tt>RewriteBase</tt>
 +
* <tt>RewriteCond</tt>
 +
* <tt>RewriteRule</tt>
  
 
== User friendly / Search engine friendly URLs ==
 
== User friendly / Search engine friendly URLs ==

Revision as of 22:42, 26 July 2006

A rewrite engine is a piece of web server software used to modify URLs, for a variety of purposes. Some benefits derived from a rewrite engine are:

  • Making website URLs more user friendly
  • Making website URLs more search-engine friendly
  • Preventing undesired "inline linking"
  • Not exposing the (web address related) inner workings of a website to users

Many of these only apply to HTTP servers whose default behaviour is to map URLs to filesystem entities (i.e. files and directories); certain environments, such as many HTTP application server platforms, make this irrelevant.

The Apache HTTP server has a rewrite engine called mod_rewrite (see below), which has been described as "the Swiss Army knife of URL manipulation".

mod_rewrite

RewriteRule FLAGS
Flag Description
R[=code] Redirect to new URL, with optional code (see below).
F Forbidden (sends 403 header)
G Gone (no longer exists)
P Proxy
L Last Rule
N Next (ie, restart rules)
C Chain
T=mime-type Set Mime Type
NS Skip if internal sub-request
NC Case insensitive
QSA Append query string
NE Do not escape output
PT Pass through
S=x Skip next x rules
E=var:value Set environmental variable "var" to "value".

Server Variables

Format

  • %{NAME_OF_VAR}

HTTP Headers

  • HTTP_USER_AGENT
  • HTTP_REFERER
  • HTTP_COOKIE
  • HTTP_FORWARDED
  • HTTP_HOST
  • HTTP_PROXY_CONNECTION
  • HTTP_ACCEPT

Request

  • REMOTE_ADDR
  • REMOTE_HOST
  • REMOTE_USER
  • REMOTE_IDENT
  • REQUEST_METHOD
  • SCRIPT_FILENAME
  • PATH_INFO
  • QUERY_STRING
  • AUTH_TYPE

Server

  • DOCUMENT_ROOT
  • SERVER_ADMIN
  • SERVER_NAME
  • SERVER_ADDR
  • SERVER_PORT
  • SERVER_PROTOCOL
  • SERVER_SOFTWARE

Time

  • TIME_YEAR
  • TIME_MON
  • TIME_DAY
  • TIME_HOUR
  • TIME_MIN
  • TIME_SEC
  • TIME_WDAY
  • TIME

Special

  • API_VERSION
  • THE_REQUEST
  • REQUEST_URI
  • REQUEST_FILENAME
  • IS_SUBREQ

Directives

  • RewriteEngine
  • RewriteOptions
  • RewriteLog
  • RewriteLogLevel
  • RewriteLock
  • RewriteMap
  • RewriteBase
  • RewriteCond
  • RewriteRule

User friendly / Search engine friendly URLs

People use website URLs in all kinds of ways. We send them to other people by email, put them on online discussion boards, or even write them on scraps of paper. This often applies not just to website home pages, but to specific content within a website. Typically website developers want to encourage this, as it means increased traffic to their sites. As such, a well designed website should allow users to enter at any URL (not just the homepage), and the URLs throughout the site should be easy to use.

A URL is easier to use if it is short but descriptive. The URL should have some text describing the content (not just numbers), but should not be too long.

Search engines will also find it easier to index pages which follow these rules. Content which is easier to index is more likely to be included in search results.

Website URLs are often quite long and quite meaningless to humans. This is because many websites have dynamic content, meaning that HTML returned to the browser is generated on-the-fly, rather than simply being stored as a static HTML file. The URL is used not only to reference an HTML document at a fixed address, but to pass pieces of data to software running on the webserver, which then generates the HTML page dynamically. Typically this software is of the form of scripts written in a web scripting language such as Perl or PHP.

Using an URL rewrite engine, the website software can be presented with URLs in one form, while actual requests (and URLs seen by the user) are in another form. So rewrite engines allow URLs to be tidied up and made more user friendly, by configuring rewrite rules, rather than modifying the webserver software.

See also

External links

Retrieved from "http://wiki.christophchamp.com/index.php?title=Rewrite_engine&oldid=2405"