The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems.^[1] HTTP is the foundation of data communication for the World Wide Web.

Hypertext is a multi-linear set of objects, building a network by using logical links (the so called hyperlinks) between the nodes (e.g. text or words). HTTP is the protocol to exchange or transfer hypertext.

The standards development of HTTP was coordinated by the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C), culminating in the publication of a series of Requests for Comments (RFCs), most notably RFC 2616 (June 1999), which defines HTTP/1.1, the version of HTTP in common use.

Technical overview[link]

HTTP functions as a request-response protocol in the client-server computing model. A web browser, for example, may be the client and an application running on a computer hosting a web site may be the server. The client submits an HTTP request message to the server. The server, which provides resources such as HTML files and other content, or performs other functions on behalf of the client, returns a response message to the client. The response contains completion status information about the request and may also contain requested content in its message body.

A web browser is an example of a user agent (UA). Other types of user agent include the indexing software used by search providers (web crawlers), voice browsers, mobile apps and other software that accesses, consumes or displays web content.

HTTP is designed to permit intermediate network elements to improve or enable communications between clients and servers. High-traffic websites often benefit from web cache servers that deliver content on behalf of upstream servers to improve response time. Web browsers cache previously accessed web resources and reuse them when possible to reduce network traffic. HTTP proxy servers at private network boundaries can facilitate communication for clients without a globally routable address, by relaying messages with external servers.

HTTP is an application layer protocol designed within the framework of the Internet Protocol Suite. Its definition presumes an underlying and reliable transport layer protocol,^[2] and Transmission Control Protocol (TCP) predominates for this purpose. However HTTP can use unreliable protocols such as the User Datagram Protocol (UDP), for example in Simple Service Discovery Protocol (SSDP).

HTTP resources are identified and located on the network by Uniform Resource Identifiers (URIs)—or, more specifically, Uniform Resource Locators (URLs)—using the http or https URI schemes. URIs and hyperlinks in Hypertext Markup Language (HTML) documents form webs of inter-linked hypertext documents. On the Internet the World Wide Web was established in 1990 by English computer scientist and innovator Tim Berners-Lee.

HTTP/1.1 is a revision of the original HTTP (HTTP/1.0). In HTTP/1.0 a separate connection to the same server is made for every resource request. HTTP/1.1 can reuse a connection multiple times to download images, scripts, stylesheets et cetera after the page has been delivered. HTTP/1.1 communications therefore experience less latency as the establishment of TCP connections presents considerable overhead.

History[link]

Tim Berners-Lee

The term HyperText was coined by Ted Nelson who in turn was inspired by Vannevar Bush's microfilm-based "memex". Tim Berners-Lee first proposed the "WorldWideWeb" project — now known as the World Wide Web. Berners-Lee and his team are credited with inventing the original HTTP along with HTML and the associated technology for a web server and a text-based web browser. The first version of the protocol had only one method, namely GET, which would request a page from a server.^[3] The response from the server was always an HTML page.^[4]

The first documented version of HTTP was HTTP V0.9 (1991). Dave Raggett led the HTTP Working Group (HTTP WG) in 1995 and wanted to expand the protocol with extended operations, extended negotiation, richer meta-information, tied with a security protocol which became more efficient by adding additional methods and header fields.^[5][6] RFC 1945 officially introduced and recognized HTTP V1.0 in 1996.

The HTTP WG planned to publish new standards in December 1995^[7] and the support for pre-standard HTTP/1.1 based on the then developing RFC 2068 (called HTTP-NG) was rapidly adopted by the major browser developers in early 1996. By March 1996, pre-standard HTTP/1.1 was supported in Arena,^[8] Netscape 2.0,^[8] Netscape Navigator Gold 2.01,^[8] Mosaic 2.7,^{[citation needed]} Lynx 2.5^{[citation needed]}, and in Internet Explorer 2.0^{[citation needed]}. End-user adoption of the new browsers was rapid. In March 1996, one web hosting company reported that over 40% of browsers in use on the Internet were HTTP 1.1 compliant.^{[citation needed]} That same web hosting company reported that by June 1996, 65% of all browsers accessing their servers were HTTP/1.1 compliant.^[9] The HTTP/1.1 standard as defined in RFC 2068 was officially released in January 1997. Improvements and updates to the HTTP/1.1 standard were released under RFC 2616 in June 1999.

HTTP session[link]

An HTTP session is a sequence of network request-response transactions. An HTTP client initiates a request by establishing a Transmission Control Protocol (TCP) connection to a particular port on a server (typically port 80; see List of TCP and UDP port numbers). An HTTP server listening on that port waits for a client's request message. Upon receiving the request, the server sends back a status line, such as "HTTP/1.1 200 OK", and a message of its own. The body of this message is typically the requested resource, although an error message or other information may also be returned.^[1]

Request methods[link]

An HTTP request made using telnet. The request, response headers and response body are highlighted.

HTTP defines nine methods (sometimes referred to as "verbs") indicating the desired action to be performed on the identified resource. What this resource represents, whether pre-existing data or data that is generated dynamically, depends on the implementation of the server. Often, the resource corresponds to a file or the output of an executable residing on the server.

HEAD

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content.

GET

Requests a representation of the specified resource. Requests using GET should only retrieve data and should have no other effect. (This is also true of some other HTTP methods.)^[1] The W3C has published guidance principles on this distinction, saying, "Web application design should be informed by the above principles, but also by the relevant limitations."^[10] See safe methods below.

POST

Submits data to be processed (e.g., from an HTML form) to the identified resource. The data is included in the body of the request. This may result in the creation of a new resource or the updates of existing resources or both.

PUT

Uploads a representation of the specified resource.

DELETE

Deletes the specified resource.

TRACE

Echoes back the received request, so that a client can see what (if any) changes or additions have been made by intermediate servers.

OPTIONS

Returns the HTTP methods that the server supports for specified URL. This can be used to check the functionality of a web server by requesting '*' instead of a specific resource.

CONNECT

Converts the request connection to a transparent TCP/IP tunnel, usually to facilitate SSL-encrypted communication (HTTPS) through an unencrypted HTTP proxy.^[11]

PATCH

Is used to apply partial modifications to a resource.^[12]

HTTP servers are required to implement at least the GET and HEAD methods^[13] and, whenever possible, also the OPTIONS method.^{[citation needed]}

Safe methods[link]

Some methods (for example, HEAD, GET, OPTIONS and TRACE) are defined as safe, which means they are intended only for information retrieval and should not change the state of the server. In other words, they should not have side effects, beyond relatively harmless effects such as logging, caching, the serving of banner advertisements or incrementing a web counter. Making arbitrary GET requests without regard to the context of the application's state should therefore be considered safe.

By contrast, methods such as POST, PUT and DELETE are intended for actions that may cause side effects either on the server, or external side effects such as financial transactions or transmission of email. Such methods are therefore not usually used by conforming web robots or web crawlers; some that do not conform tend to make requests without regard to context or consequences.

Despite the prescribed safety of GET requests, in practice their handling by the server is not technically limited in any way. Therefore, careless or deliberate programming can cause non-trivial changes on the server. This is discouraged, because it can cause problems for Web caching, search engines and other automated agents, which can make unintended changes on the server.

Idempotent methods and web applications[link]

Methods PUT and DELETE are defined to be idempotent, meaning that multiple identical requests should have the same effect as a single request (Note that idempotence refers to the state of the system after the request has completed, so while the action the server takes (e.g. deleting a record) or the response code it returns may be different on subsequent requests, the system state will be the same every time.) Methods GET, HEAD, OPTIONS and TRACE, being prescribed as safe, should also be idempotent, as HTTP is a stateless protocol.^[1]

In contrast, the POST method is not necessarily idempotent, and therefore sending an identical POST request multiple times may further affect state or cause further side effects (such as financial transactions). In some cases this may be desirable, but in other cases this could be due to an accident, such as when a user does not realize that their action will result in sending another request, or they did not receive adequate feedback that their first request was successful. While web browsers may show alert dialog boxes to warn users in some cases where reloading a page may re-submit a POST request, it is generally up to the web application to handle cases where a POST request should not be submitted more than once.

Note that whether a method is idempotent is not enforced by the protocol or web server. It is perfectly possible to write a web application in which (for example) a database insert or other non-idempotent action is triggered by a GET or other request. Ignoring this recommendation, however, may result in undesirable consequences, if a user agent assumes that repeating the same request is safe when it isn't.

Security[link]

Implementing methods such as TRACE, TRACK and DEBUG is considered potentially insecure by some security professionals, because they can be used by attackers to gather information or bypass security controls during attacks. Security software tools such as Tenable Nessus and Microsoft URLScan report on the presence of these methods as being security issues.

Status codes[link]

In HTTP/1.0 and since, the first line of the HTTP response is called the status line and includes a numeric status code (such as "404") and a textual reason phrase (such as "Not Found"). The way the user agent handles the response primarily depends on the code and secondarily on the response headers. Custom status codes can be used since, if the user agent encounters a code it does not recognize, it can use the first digit of the code to determine the general class of the response.^[14]

Also, the standard reason phrases are only recommendations and can be replaced with "local equivalents" at the web developer's discretion. If the status code indicated a problem, the user agent might display the reason phrase to the user to provide further information about the nature of the problem. The standard also allows the user agent to attempt to interpret the reason phrase, though this might be unwise since the standard explicitly specifies that status codes are machine-readable and reason phrases are human-readable.

Persistent connections[link]

In HTTP/0.9 and 1.0, the connection is closed after a single request/response pair. In HTTP/1.1 a keep-alive-mechanism was introduced, where a connection could be reused for more than one request. Such persistent connections reduce request latency perceptibly, because the client does not need to re-negotiate the TCP connection after the first request has been sent. Another positive side effect is that in general the connection becomes faster with time due to TCP's slow-start-mechanism.

Version 1.1 of the protocol also made bandwidth optimization improvements to HTTP/1.0. For example, HTTP/1.1 introduced chunked transfer encoding to allow content on persistent connections to be streamed rather than buffered. HTTP pipelining further reduces lag time, allowing clients to send multiple requests before waiting for each response. Another improvement to the protocol was byte serving, where a server transmits just the portion of a resource explicitly requested by a client.

HTTP session state[link]

HTTP is a stateless protocol. A stateless protocol does not require the server to retain information or status about each user for the duration of multiple requests. For example, when a web server is required to customize the content of a web page for a user, the web application may have to track the user's progress from page to page. A common solution is the use of HTTP cookies. Other methods include server side sessions, hidden variables (when the current page contains a form), and URL-rewriting using URI-encoded parameters, e.g., /index.php?session_id=some_unique_session_code.

Secure HTTP[link]

There are three methods of establishing a secure HTTP connection: HTTP Secure, Secure Hypertext Transfer Protocol and the HTTP/1.1 Upgrade header. Browser support for the latter two is, however, nearly non-existent,^{[citation needed]} so HTTP Secure is the dominant method of establishing a secure HTTP connection.

Request message[link]

The request message consists of the following:

• A request line, for example GET /images/logo.png HTTP/1.1, which requests a resource called /images/logo.png from the server.
• Headers, such as Accept-Language: en
• An empty line.
• An optional message body.

The request line and headers must all end with <CR><LF> (that is, a carriage return followed by a line feed). The empty line must consist of only <CR><LF> and no other whitespace.^[15] Although <CR><LF> is required <LF> alone is also accepted by most servers.^{[citation needed]} In the HTTP/1.1 protocol, all headers except Host are optional.

A request line containing only the path name is accepted by servers to maintain compatibility with HTTP clients before the HTTP/1.0 specification in RFC 1945.^[16]

Response message[link]

The response message consists of the following:

• A Status-Line (for example HTTP/1.1 200 OK, which indicates that the client's request succeeded)
• Headers, such as Content-Type: text/html
• An empty line
• An optional message body

The Status-Line and headers must all end with <CR><LF> (a carriage return followed by a line feed). The empty line must consist of only <CR><LF> and no other whitespace.^[17]

Example session[link]

Below is a sample conversation between an HTTP client and an HTTP server running on www.example.com, port 80.

Client request[link]

 GET /index.html HTTP/1.1␍␊
 Host: www.example.com␍␊
 ␍␊

A client request (consisting in this case of the request line and only one header) is followed by a blank line, so that the request ends with a double newline, each in the form of a carriage return followed by a line feed. The "Host" header distinguishes between various DNS names sharing a single IP address, allowing name-based virtual hosting. While optional in HTTP/1.0, it is mandatory in HTTP/1.1.

Server response[link]

 HTTP/1.1 200 OK
 Date: Mon, 23 May 2005 22:38:34 GMT
 Server: Apache/1.3.3.7 (Unix) (Red-Hat/Linux)
 Last-Modified: Wed, 08 Jan 2003 23:11:55 GMT
 Etag: "3f80f-1b6-3e1cb03b"
 Accept-Ranges:  none
 Content-Length: 438
 Connection: close
 Content-Type: text/html; charset=UTF-8

The ETag (entity tag) header is used to determine if a cached version of the requested resource is identical to the current version of the resource on the server. Content-Type specifies the Internet media type of the data conveyed by the HTTP message, while Content-Length indicates its length in bytes. The HTTP/1.1 webserver publishes its ability to respond to requests for certain byte ranges of the document by setting the header Accept-Ranges: bytes. This is useful, if the client needs to have only certain portions^[18] of a resource sent by the server, which is called byte serving. When Connection: close is sent in a header, it means that the web server will close the TCP connection immediately after the transfer of this response.

Most of the header lines are optional. When Content-Length is missing the length is determined in other ways. Chunked transfer encoding uses a chunk size of 0 to mark the end of the content. Identity encoding without Content-Length reads content until the socket is closed.

A Content-Encoding like gzip can be used to compress the transmitted data.

See also[link]

HTTP replacements or enhancements[link]

• Representational State Transfer (REST)
• SPDY - A HTTP enhancement proposed by Google
• Waka (protocol) - A HTTP replacement proposed by Roy Fielding
• HTTP-MPLEX - A backwards compatible enhancement to HTTP to improve page and web object retrieval time in congested networks proposed by Robert Mattson
• HTTP 2.0 - currently being worked on by the IETF's Hypertext Transfer Protocol Bis (httpbis) working group.^[19]
• Constrained Application Protocol - A semantically similar protocol to HTTP but used UDP or UDP-like messages targeted for devices with limited processing capability. Re-uses HTTP and other internet concepts like Internet media type and web linking (http://tools.ietf.org/html/rfc5988).

Further Information[link]

• Basic access authentication
• Content negotiation
• HTTP compression
• Hxxp

Related topics and technologies[link]

• Curl-loader - HTTP/S loading/testing open-source SW
• Digest access authentication
• List of file transfer protocols
• List of HTTP headers
• List of HTTP status codes
• Web cache
• WebDAV

References[link]

Further reading[link]

• HTTP 0.9 - As Implemented in 1991

External links[link]

Wikimedia Commons has media related to: HTTP

• "Change History for HTTP". W3.org. http://www.w3.org/Protocols/History.html. Retrieved 2010-08-01.  A detailed technical history of HTTP.
• "Design Issues for HTTP". W3.org. http://www.w3.org/Protocols/DesignIssues.html. Retrieved 2010-08-01.  Design Issues by Berners-Lee when he was designing the protocol.
• "Classic HTTP Documents". W3.org. 1998-05-14. http://www.w3.org/Protocols/Classic.html. Retrieved 2010-08-01.  list of other classic documents recounting the early protocol history

Look up put in Wiktionary, the free dictionary.

Put can refer to:

• Put option, a financial contract between two parties, the buyer and the seller of the option
• The Biblical Put, the son of Ham and the grandson of Noah. See the article Phut
• A type of HTTP request used for uploading files to a specified URI on a web-server
• The FTP option that copies a file from the local system to the remote system (as compared to "get")
• Put (band), from Rijeka, Croatia
• Put, a 16th century card game
• The command: put "..." in Turing (programming language)

PUT may also be an acronym referring to:

• A Programmable Unijunction Transistor
• Products Under Test, products being considered for DivX certification
• Petroleum University of Technology, a university in Abadan, Ahvaz, Mahmud Abad and Tehran, Iran
• Poznań University of Technology, a university located in Poznań, Poland

See also[link]

• puts and puts(), a simple function in C that puts text on the screen

This disambiguation page lists articles associated with the same title. If an internal link led you here, you may wish to change the link to point directly to the intended article.

This biographical article needs additional citations for verification. Please help by adding reliable sources. Contentious material about living persons that is unsourced or poorly sourced must be removed immediately, especially if potentially libelous or harmful. (July 2012)

ZZ Ward is an American singer, musician and songwriter signed to the Boardwalk Entertainment Group and Hollywood Records. ZZ Ward is also managed by E. Kidd Bogart's Boardwalk Music Group. She released her debut EP, Criminal, on May 8, 2012. Her debut album is scheduled for release in September 2012.

History[link]

ZZ was born in Abington, PA where she lived as a child before moving to Roseburg, OR where she joined her first band at the age of 12. She moved to LA and signed to E. Kidd Bogart's Boardwalk Entertainment Group after which she began work on her debut album which included work with Ryan Tedder, Pete Rock, Ali Shaheed Muhammad, and Fitz of Fitz and the Tantrums^[1]. While making the Criminal EP, ZZ also began work on Eleven Roses, a free mixtape on which she offered her interpretations of recent tracks by Kendrick Lamar, Childish Gambino and Tyler, the Creator^[2]. For “Criminal” she borrowed the beat from “Oil Money” by Freddie Gibbs, who was so impressed by Ward’s remake that he asked to contribute a guest verse to the official version on the EP. The Criminal EP was released in May of 2012, and features the songs "Til the Casket Drops" (featured in the TV promo campaign for the current season of ABC Family's Pretty Little Liars)^[3], "Put the Gun Down", "Move Like U Stole It", and "Criminal" (feat. Freddie Gibbs). ZZ's debut album will be released this fall^[4].

Discography[link]

Studio albums[link]

• TBD (Sept., 2012)

EPs[link]

• "Criminal (May 8, 2012)

Track listing

1. "Til the Casket Drops" - 3:08
2. "Put the Gun Down" - 2:50
3. "Criminal (feat. Freddie Gibbs)" - 3:51
4. "Move Like U Stole It" - 3:20

Mixtapes[link]

• "Eleven Roses" (Feb. 1, 2012)

Track listing

1. "Better Off Dead" - 2:49
2. "Got It Bad" - 2:44
3. "OVERdUe" - 2:37
4. "Criminal" - 2:42
5. "Morphine" - 2:38
6. "Cinnamon Stix" - 2:20
7. "Til the Casket Drops (live acoustic)" - 3:03
8. "Last Love Song (acoustic)" - 3:27

See also[link]

• List of current Hollywood Records artists

External links[link]

• Official website
• Official Facebook
• Official Twitter

References[link]

[[Category:People from Roseburg, Oregon]

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (August 2008)

Fedde le Grand
Fedde Le Grand
Background information
Birth name	Fedde le Grand
Born	(1977-09-07) 7 September 1977 (age 34) Utrecht, Netherlands
Genres	Eurodance, House, Electro house, Tech House, Techno
Occupations	DJ, producer Fiancè- Tana StCyr 2002-Current
Years active	2003-present
Labels	Flamingo Recordings, Ministry of Sound Australia, Toolroom Records
Website	Official Web Site

Fedde le Grand (born 7 September 1977) is a Dutch house DJ and producer whose single "Put Your Hands Up For Detroit" (UK/US) / "Put Your Hands Up 4 Detroit"^[1] (Europe, excluding UK) reached number one on the UK's singles and the top 5 in the Dutch singles chart, and spent five weeks in the Spanish dance chart. On 28 October 2009, DJ Magazine announced the results of their annual Top 100 DJ Poll, with Ultra Records artist Fedde le Grand placed at #29.,^[2] climbing to #21 in 2010 and #14 in 2011.

Biography[link]

1998 - 2000[link]

Inspired by Masters At Work and Mousse T, Fedde le Grand kicks off his DJ career in the Danssalon in Eindhoven. For two years he is the resident DJ on the Sunday night. He also plays Dutch clubs like Panama, the Escape and the Love Boat in Amsterdam, and Jackies, Thalia, Discothèque and Now & Wow in Rotterdam, De Rechter in Eindhoven and he can also be seen at Extrema. Fedde le Grand is also popular abroad and performs in Britain, France, Germany, Spain, Russia, Greece and Israel.

2001 - 2006[link]

From 2001 Fedde le Grand works on his own productions. His first release, under the name F.L.G., is the Electronic EP on Flamingo Recordings, a co-production with Robin M and with contributions from Funkerman (Ardie van Beek). Le Grand's records are released on labels such as Little Mountain Recordings (Sander Kleinenberg's label), Influence, Work and the British labels CR2 Records and Toolroom. Le Grand makes remixes for artists like Anita Kelsey (Every Kiss, 2004), Erick E (Boogie Down, 2005 and The Beat Is Rockin', 2006), Funkerman (The One, 2005), Olav Basoski (Proper Tunes, 2006) and Camille Jones (The Creeps, 2006). The DJ is a regular guest in Dutch radio show Ministry of Beats on 3FM radio. Put Your Hands Up 4 Detroit (2006), an electro track with vocals by Mc Gee, is officially awarded 'the summer anthem of Ibiza 2006'. The single climbs to the top slot of the UK charts and is also a big dance hit in the Netherlands, Belgium, Germany and Australia. Hiphop crew D12 from Detroit (known for their work with Eminem) puts out a vocal version of the hit record. Le Grand provides a remix for Robbie Williams' single Bongo Bong/Je Ne T'Aime Plus.

2007[link]

In March the DJ commences an Australian tour and as of May he tours the US. Fedde le Grand wins three prizes at the International Dance Music Awards staged at the Winter Music Conference in Miami (March). Not only he is Best Breakthrough Solo Artist, but also his hit Put Your Hands Up For Detroit is awarded in the categories Best Breaks/Electro Track and Best Underground Dance Track. On March 31 he receives a Danish Dance Award. On July Fedde le Grand he appears at Amsterdam's Westerpark edition of the worldwide Live Earth festival, supervised by climate guru Al Gore, who raises awareness for the global warming problem. Especially for this event Fedde le Grand writes the Mirror070707 Anthem. The festival is broadcast live on public Nederland 3 (TV) en 3FM (radio). At the same day Le Grand is prominently on the bill of dance event Sensation White at the Amsterdam Arena. During the tenth edition of the DJ Awards on Ibiza, Fedde Le Grand wins in the category Breakthrough. Le Grand's remix of Let Me Think About It, sung by Danish singer Ida Corr, reaches the Top 3 of the British charts. This makes it the third British hit single for the producer within a year. In the annual Top 100 of the influential British DJ Mag Le Grand the 22nd place which makes him the Highest New Entry. Under the name The Flamingo Project the single Take No Shhhhhhhh is released.

2008[link]

Fedde le Grand's club hit Put Your Hands Up For Detroit is mixed with Madonna's Music during the opening of Madonna's live shows. The American singer asks Le Grand to do a remix of her single Give It 2 Me, which is to be released in July. After Junkie XL Fedde Le Grand is now the second Dutchman to do a remix for Madonna.

2009[link]

The title track of Le Grand's debut album Output (September) is used in the promo videos of the OUTPUT World Tour and the Flamingo Nights. It's also being played by the DJ during the Ultra Festival in March in Miami. The first single of the album is released in May: Scared of Me, with vocals by Mitch Crown and a remix by Dutch producer Hardwell (Robbert van de Corput). Mitch Crown can also be heard on the Let Me Be Real (August). One of the remixes of the fusion between pop and dance is done by Kraak & Smaak.

2010[link]

The single Back & Forth has vocals by MC Mr. V. from New York (real name: Victor Font), whom Fedde Le Grand has met at the Miami Winter Music Conference in 2008. Le Grand again travels around the world for performances. He plays in Las Vegas and Chicago (January), Lausanne, Lyon, Munich, Bangkok and Jakarta (February), São Paulo and Miami (March), Casablanca, Berlin, Budapest, Birmingham and Düsseldorf (April), Hong Kong, Singapore, Quebec, Toronto, Seattle and San Francisco (May), Ibiza, London, Los Angeles and Broek op Langendijk (June). The DJ has just finished his set at the Love Parade in Duisburg, Germany, on 24 July, when 20 people are crushed to death at the entrance to the festival grounds. He offers his condolences to the victims on Twitter. The world tour continues in July and Augustus with performances in England, France, Turkey, Lebanon, Italy, Switzerland, Germany, Greece, Spain, Belgium, Bulgaria, Macedonia and Romania. A tour around the USA with stop in New York, Los Angeles, and The Necto (nightclub) in Ann Arbor.

Discography[link]

Studio albums[link]

Singles[link]

External links[link]

• Official website
• Fedde le Grand's channel on YouTube
• Artist Site at Ultra Records

References[link]

1. ^ IMO Records "Fedde le Grand Biography", IMO Records,Retrieved on 11 February 2012.
2. ^ "DJ Mag's Top 100 DJ's". DJ Magazine. http://www.djmag.com/top100. Retrieved 19 November 2009. 

Ariana Grande
Grande at the film premiere of Harry Potter and the Deathly Hallows – Part 2 in July 2011
Background information
Birth name	Ariana Grande-Butera
Born	(1993-06-26) June 26, 1993 (age 19) Boca Raton, Florida, U.S.
Genres	Pop
Occupations	Actress, singer, dancer
Years active	2008–present
Labels	Universal Republic
Website	arianagrande.info[1]

Ariana Grande-Butera^[2][3] (born June 26, 1993^[4][5]) is an American actress, singer, and dancer. She made her performance debut on Broadway at age 15. Recently, she has gained attention for her role as Cat Valentine on the Nickelodeon sitcom Victorious.