
A rewrite engine is software which modifies a web URL's appearance (URL rewriting). Users of web applications prefer short, neat URLs to raw query string parameters. A concise URL is easy to remember, and less time-consuming to type in. If the URL can be made to relate clearly to the content of the page, then errors are less likely to happen.
Search engine friendly URLs (for short SEF URLs) are implemented with Rewrite engines.
URL rewriting is not URL redirection.
Contents |
This URL contains query string parameters to encode the date for which some blog engines should show available postings
but can be altered to give the user a clear idea of what he or she is going to see
The second address also allows the user to change the URL to see all postings available in December, simply by removing the text encoding the day '10', and thereby saving having to navigate the GUI.
Another example might be changing
to...
The benefits of a rewrite engine are[1]:
Known drawbacks:
In Java, the term "URL rewriting" sometimes describes a Web Application Server adding a session id to a URL when cookies are not supported (e.g. "index.jsp" is rewritten to "index.jsp;jsessionid=xyc" when the links are drawn in an HTML page).
Recent generations of web frameworks usually include URL rewriting: Ruby on Rails has built-in URL rewriting via Routes[2], Django uses a regular-expressions based system[3], Java's Stripes Framework used to require a third-party extension[4] but integrated the module in the core distribution with Stripes 1.5[5]
Apache Software Foundation's Apache HTTP server
Microsoft's Internet Information Server (IIS)
Java 2 Platform, Enterprise Edition (J2EE) Servlet container servers (such as Apache Tomcat, Resin, Orion etc):
Why are we here?
All text is available under the terms of the GNU Free Documentation License
This page is cache of Wikipedia. History