+
What is Stack?
+
+ Stack is a convention for composing HttpKernelInterface middlewares.
+
+
+ 
+
+
+ By wrapping your application in decorators you can add new behaviour from the outside.
+
-
Example
-
use Symfony\Component\HttpFoundation\Request;
-use Symfony\Component\HttpKernel\HttpCache\Store;
+
+
Supported frameworks
+
+ {% spaceless %}
+
+ {% endspaceless %}
-// This can be **any** HttpKernelInterface based application
-$app = new Silex\Application();
-$app->get('/', function () {
- return 'Hello World!';
-});
+
+ See the full list on symfony.com
+
+
-// Front controller is business as usual
-$request = Request::createFromGlobals();
-$response = $app->handle($request)->send();
-$app->terminate($request, $response);
+
+
Conventions
+
+ A stack middleware is just an object that follows these conventions:
+
+
+ 1
Implement the HttpKernelInterface2
Take the decorated app as the first constructor argument3
Decorate the handle call, delegate to the decorated app
+
+
+ Yes, leveraging the HTTP interface is that easy!
+
{% endblock %}
+{% block footer %}
+
Brought to you by
+
+{% endblock %}
diff --git a/source/media.html b/source/media.html
new file mode 100644
index 0000000..fe4f956
--- /dev/null
+++ b/source/media.html
@@ -0,0 +1,20 @@
+---
+layout: default
+title: Media
+nav_name: media
+---
+{% block content %}
+
+
Forum PHP 2013
+
+
+ Symfony Live London 2013
+
+
+ Symfony Live Portland 2013
+
+
+ Symfony Usergroup Zürich
+
+
+{% endblock %}
diff --git a/source/middlewares.html b/source/middlewares.html
new file mode 100644
index 0000000..1a786ba
--- /dev/null
+++ b/source/middlewares.html
@@ -0,0 +1,308 @@
+---
+layout: default
+title: Community Middlewares
+nav_name: middlewares
+---
+{% block content %}
+
+
Community Middlewares
+
+
+
+
+ by symfony
+
+
The Symfony2 cache system relies on the simplicity and power of the HTTP cache as defined in the HTTP specification.
+
+
+
+
+
+ by laravel
+
+
The laravel cookie guard encrypts outgoing cookies.
+
+
+
+
+
+
+
+ by geocoder
+
+
Adds geolocation results to the request for subsequent middlewares. Can use any geocoding provider from Geocoder.
+
+
+
+
+
+ by alsar
+
+
Stack middleware for restricting application access to specific IP addresses.
+
+
+
+
+
+
+
+ by atst
+
+
Stack middleware for displaying maintenance pages.
+
+
+
+
+
+ by igorw
+
+
+ OAuth authentication.
+
+
+
+
+
+
+
+
+ by dflydev
+
+
+ Provides HTTP Basic Authentication following STACK-2 Authentication conventions.
+
+
+
+
+
+
+ by dflydev
+
+
+ Provides Hawk authentication following STACK-2 Authentication conventions.
+
+
+
+
+
+
+
+
+ by asm89
+
+
+ Cross-origin resource sharing.
+
+
+
+
+
+
+ by dongilbert
+
+
+ Provides a default robots.txt for non-production environments.
+
+
+
+
+
+
+
+
+ by willdurand
+
+
+ Content negotiation made easy.
+
+
+
+
+
+
+ by CHH
+
+
+ Inserts a trap for spam bots into responses and catches bots
+ and then gives them a blank page.
+
+
+
+
+
+
+
+
+ by Helthe
+
+
+ Stack middleware for Turbolinks.
+
+
+
+
+
+
+ by h4cc
+
+
+ Stack Middleware for logging Requests and Responses to a PSR-3 Logger.
+
+
+
+
+
+
+
+
+ by penoonan
+
+
+ Stack Middleware for throttling requests by IP.
+
+
+
+
+
+
+ by moufmouf
+
+
+ Stack Middleware for using the Whoops error handling library.
+
+
+
+
+
+
+
+
+ by moufmouf
+
+
+ Turns a Silex application into a Stack middleware.
+
+
+
+
+
+
+ by moufmouf
+
+
+ Turns a Symfony 2 application (i.e. Kernel) into a Stack middleware.
+
+
+
+
+
+
+
+
+ by h4cc
+
+
+ Converting PSR-7 and Symfony Http Foundation back and forth.
+
+
+
+
+
+
+
+{% endblock %}
diff --git a/source/specs.html b/source/specs.html
new file mode 100644
index 0000000..059a947
--- /dev/null
+++ b/source/specs.html
@@ -0,0 +1,64 @@
+---
+layout: default
+title: Conventions and Protocols
+nav_name: specs
+---
+{% block content %}
+
+
+ Conventions and Protocols
+
+
+ In order to further the goal of interoperability between disparate
+ HttpKernelInterface implementations, Stack maintains a list
+ of community driven proposals for Stack conventions and protocols.
+
+
+
+
+
+
+ Specification for how community driven Stack proposals will be
+ written and managed.
+
+
+
+
+
+
+ Specification for writing and interacting with Stack middlewares
+ and applications.
+
+
+
+
+
+
+
+
+ Specification for authentication middlewares to follow in order
+ for applications and authorization middlewares to be able to
+ interact with each other.
+
+
+
+
+
+
+ Specification for authorization middlewares to follow in order
+ for applications and authentication middlewares to be able to
+ interact with each other.
+
+
+
+
+
+{% endblock %}
diff --git a/source/specs/STACK-0.md b/source/specs/STACK-0.md
new file mode 100644
index 0000000..8c36d23
--- /dev/null
+++ b/source/specs/STACK-0.md
@@ -0,0 +1,32 @@
+---
+layout: spec
+title: STACK-0 Proposals
+status: draft
+---
+
+Specification for how community driven Stack proposals will be written and
+managed.
+
+ * Name: {{ page.title }}
+ * Editor: Beau Simensen <[beau@dflydev.com](mailto:beau@dflydev.com)>
+
+
+### Language
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
+"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
+interpreted as described in [RFC 2119](http://www.ietf.org/rfc/rfc2119.txt).
+
+
+### Goals
+
+ * To define a workflow for community driven Stack proposals.
+
+
+### Identification
+
+ * Each proposal MUST have an identifier that MUST follow the format of
+ `STACK-{NUMBER}`. The number SHOULD just be the next available number but it MAY
+ be a special number.
+ * Each proposal MUST have a descriptive name that either names the subject of
+ the proposal or otherwise succinctly defines the focus of the proposal.
diff --git a/source/specs/STACK-1.md b/source/specs/STACK-1.md
new file mode 100644
index 0000000..3184cc6
--- /dev/null
+++ b/source/specs/STACK-1.md
@@ -0,0 +1,24 @@
+---
+layout: spec
+title: STACK-1 Core
+status: draft
+---
+
+Specification for writing and interacting with Stack middlewares and
+applications.
+
+ * Name: {{ page.title }}
+ * Editor: Beau Simensen <[beau@dflydev.com](mailto:beau@dflydev.com)>
+
+
+### Language
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
+"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
+interpreted as described in [RFC 2119](http://www.ietf.org/rfc/rfc2119.txt).
+
+
+### Goals
+
+ * Specify requirements for a Stack middleware
+
diff --git a/source/specs/STACK-2.md b/source/specs/STACK-2.md
new file mode 100644
index 0000000..efc00ef
--- /dev/null
+++ b/source/specs/STACK-2.md
@@ -0,0 +1,82 @@
+---
+layout: spec
+title: STACK-2 Authentication
+status: draft
+---
+
+This document proposes conventions for authentication middlewares to follow in
+order for applications and authorization middlewares to be able to interact
+with each other.
+
+ * Name: {{ page.title }}
+ * Editor: Beau Simensen <[beau@dflydev.com](mailto:beau@dflydev.com)>
+
+
+### Language
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
+"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
+interpreted as described in [RFC 2119](http://www.ietf.org/rfc/rfc2119.txt).
+
+
+### Goals
+
+ * To allow authentication middlewares to communicate when a request has been
+ authenticated.
+ * To allow other middlewares or applications to communicate whether or not
+ the authentication was accepted (for example, authorization failed or is
+ required).
+ * To allow for some coexistence between multiple Stack authentiation
+ middlewares for the same request.
+
+
+### Stack Authentication Middlewares
+
+#### Token
+
+A Stack authentication token represents the user or service driving the user
+agent making a request. The token MUST be stored as the `stack.authn.token`
+request attribute. The token MUST either be a string or serializable.
+
+
+#### Authentication
+
+A Stack authentication middleware is free to use whatever means necessary to
+authenticate a request. The end result of a successfully authenticated request
+should be that the `stack.authn.token` attribute on the request is set to a
+valid token.
+
+If a request has authentication credentials that are invalid for any reason a
+Stack authentication middleware MAY either immediately challenge or return
+another response (for example, a 400 error response).
+
+If a request already has the `stack.authn.token` attribute set a Stack
+authentication middleware MUST NOT attempt to further authenticate the request.
+However, the Stack authentication middleware MAY act further upon inspecting
+the response.
+
+
+#### Integration with Stack Authorization
+
+Stack authentication middlewares SHOULD inspect the response from the wrapped
+app to see if it has a status code of `401` and a `WWW-Authenticate: Stack`
+header. In this case, the Stack authentication middleware can use its own best
+judgement to determine whether or not it should issue a challenge.
+
+Modifying or replacing the response is allowed but a Stack authentication
+middleware MUST NOT challenge unless the response is in this state. If a Stack
+authentication middleware does not change the `WWW-Authenticate` value other
+Stack authentication middlewares will be given an opportunity to challenge.
+
+
+### Implementations
+
+ * [dflydev/stack-authentication](https://github.com/dflydev/dflydev-stack-authentication)
+ A collection of middlewares designed to help authentication middleware
+ implementors adhere to the STACK-2 Authentication conventions.
+ * [dflydev/stack-hawk](https://github.com/dflydev/dflydev-stack-hawk)
+ [Hawk](https://github.com/hueniverse/hawk) authentication middleware.
+ * [dflydev/stack-basic-authentication](https://github.com/dflydev/dflydev-stack-basic-authentication)
+ HTTP Basic Authentication middleware.
+ * [jsor/stack-jwt](https://github.com/jsor/stack-jwt)
+ JSON Web Token (JWT) authentication middleware.
diff --git a/source/specs/STACK-3.md b/source/specs/STACK-3.md
new file mode 100644
index 0000000..c0c4456
--- /dev/null
+++ b/source/specs/STACK-3.md
@@ -0,0 +1,48 @@
+---
+layout: spec
+title: STACK-3 Authorization
+status: draft
+---
+
+This document proposes conventions for authorization middlewares to follow in
+order for applications and authentication middlewares to be able to interact
+with each other.
+
+ * Name: {{ page.title }}
+ * Editor: Beau Simensen <[beau@dflydev.com](mailto:beau@dflydev.com)>
+
+
+### Language
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
+"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
+interpreted as described in [RFC 2119](http://www.ietf.org/rfc/rfc2119.txt).
+
+
+### Goals
+
+ * To instruct authorization middlewares on how to determine if a request has
+ been authenticated by a Stack authentication middleware.
+ * To instruct authorization middlewares on how to respond in the event that
+ authorization fails when a request is authenticated.
+ * To instruct authorization middlewares on how to respond in the event that
+ authorization fails when a request is not authenticated.
+
+
+### Stack Authorization Middlewares and Applications
+
+Authorization MUST be based on the token stored in the `stack.authn.token`
+request attribute.
+
+If a token exists but the request is not authorized, a Stack authorization
+middleware MUST return a `403` response.
+
+If a token does not exist, a Stack authorization middleware SHOULD return a
+`401` response with a `WWW-Authenticate: Stack` header. This will give the
+appropriate Stack authentication middlewares an opportunity to challenge as
+appropriate.
+
+
+### Implementations
+
+ * None
diff --git a/source/toolbox.html b/source/toolbox.html
new file mode 100644
index 0000000..c7e6b98
--- /dev/null
+++ b/source/toolbox.html
@@ -0,0 +1,56 @@
+---
+layout: default
+title: The Toolbox
+nav_name: toolbox
+---
+{% block content %}
+
+{% endblock %}