SUPPORT THE WORK

GetWiki

rewrite engine

ARTICLE SUBJECTS
aesthetics  →
being  →
complexity  →
database  →
enterprise  →
ethics  →
fiction  →
history  →
internet  →
knowledge  →
language  →
licensing  →
linux  →
logic  →
method  →
news  →
perception  →
philosophy  →
policy  →
purpose  →
religion  →
science  →
sociology  →
software  →
truth  →
unix  →
wiki  →
ARTICLE TYPES
essay  →
feed  →
help  →
system  →
wiki  →
ARTICLE ORIGINS
critical  →
discussion  →
forked  →
imported  →
original  →
rewrite engine
[ temporary import ]
please note:
- the content below is remote from Wikipedia
- it has been imported raw for GetWiki
{{Selfref|In Wikipedia and other MediaWiki sites, see .}}{{primary sources|date=January 2011}}A rewrite engine is a software component that performs rewriting on Uniform Resource Locators, modifying their appearance. This modification is called URL rewriting. It is a way of implementing URL mapping or routing within a web application. The engine is typically a component of a web server or web application framework. Rewritten URLs (sometimes known as short, pretty or fancy URLs, search engine friendly - SEF URLs, or slugs) are used to provide shorter and more relevant-looking links to web pages. The technique adds a layer of abstraction between the files used to generate a web page and the URL that is presented to the outside world.

Usage

{{see also|Semantic URL|URL shortening}}Web sites with dynamic content can use URLs that generate pages from the server using query string parameters. These are often rewritten to resemble URLs for static pages on a site with a subdirectory hierarchy. For example, the URL to a wiki page might be: but can be rewritten as: A blog might have a URL that encodes the dates of each entry: It can be altered like this: which also allows the user to change the URL to see all postings available in December, simply by removing the text encoding the day '19', as though navigating "up" a directory: A site can pass specialized terms from the URL to its search engine as a search term. This would allow users to search directly from their browser. For example, the URL as entered into the browser's location bar:
weblink term
Will be urlencoded by the browser before it makes the HTTP request. The server could rewrite this to:

Benefits and drawbacks

{{Section OR|date=April 2013}}There are several benefits to using URL rewriting:Many of these only apply to HTTP servers whose default behavior 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 links are "cleaner" and more descriptive, improving their "friendliness" to both users and search engines.
  • They prevent undesired "inline linking", which can waste bandwidth.
  • The site can continue to use the same URLs even if the underlying technology used to serve them is changed (for example, switching to a new blogging engine).
There can, however be drawbacks as well; if a user wants to modify a URL to retrieve new data, URL rewriting may hinder the construction of custom queries due to the lack of named variables. For example, it may be difficult to determine the date from the following format: In this case, the original query string was more useful, since the query variables indicated month and day:

Web frameworks

Many web frameworks include URL rewriting, either directly or through extension modules. From a software development perspective, URL rewriting can aid in code modularization and control flow,WEB, Clean URL,weblink DocForge, 25 April 2014, making it a useful feature of modern web frameworks.

See also

Notes

{{reflist|2}}

External links



- content above as imported from Wikipedia
- "rewrite engine" does not exist on GetWiki (yet)
- time: 6:07am EDT - Mon, Jun 18 2018
[ this remote article is provided by Wikipedia ]
LATEST EDITS [ see all ]
GETWIKI 09 MAY 2016
GETWIKI 18 OCT 2015
M.R.M. Parrott
Biographies
GETWIKI 20 AUG 2014
GETWIKI 19 AUG 2014
GETWIKI 18 AUG 2014
Wikinfo
Culture
CONNECT