High-level HTTP Server

New in version 0.10.

Run a simple web server

For implementing web server at first create request handler.

Handler is a coroutine or regular function that accepts only request parameter of type Request and returns Response instance:

import asyncio
from aiohttp import web

@asyncio.coroutine
def hello(request):
    return web.Response(request, b"Hello, world")

Next you have to create Application instance and register handler in application’s router pointing HTTP method, path and handler:

app = web.Application()
app.router.add_route('GET', '/', hello)

After that create server and run asyncio loop as usual:

loop = asyncio.get_event_loop()
f = loop.create_server(app.make_handler, '0.0.0.0', '8080')
srv = loop.run_until_complete(f)
print('serving on', srv.sockets[0].getsockname())
try:
    loop.run_forever()
except KeyboardInterrupt:
    pass

That’s it.

Router

Router is any object that implements AbstractRouter interface.

aiohttp.web provides single implementation called UrlDispatcher.

Application uses UrlDispatcher as router() by default.

Handler

Handler is an any callable that accepts single Request argument and returns StreamResponse derived (e.g. Response) instance.

Handler can be a coroutine, aiohttp.web will unyield returned result by applying yield from to handler.

Handlers can be first-class functions like:

@asyncio.coroutine
def hello(request):
    return web.Response(request, b"Hello, world")

app.router.add_route('GET', '/', hello)

Sometimes you would like to group logically coupled handlers into python class.

aiohttp.web doesn’t dictate any implementation details, application developer can use classes if he want:

class Handler:

    def __init__(self):
        pass

    def handle_intro(self, request):
        return web.Response(request, b"Hello, world")

    @asyncio.coroutine
    def handle_greeting(self, request):
        name = request.match_info.get('name')
        txt = "Hello, {}".format(name)
        return web.Response(request, txt.encode('utf-8')

handler = Handler()
app.router.add_route('GET', '/intro', handler.handle_intro)
app.router.add_route('GET', '/greet/{name}', handler.handle_greeting)

File Uploads

There are two parts necessary for handling file uploads. The first is to make sure you have a form that’s been setup correctly to accept files. This means adding enctype attribute to your form element with the value of multipart/form-data. A very simple example would be a form that accepts an mp3 file. Notice we’ve setup the form as previously explained and also added an input element of the file type:

<form action="/store_mp3" method="post" accept-charset="utf-8"
      enctype="multipart/form-data">

    <label for="mp3">Mp3</label>
    <input id="mp3" name="mp3" type="file" value="" />

    <input type="submit" value="submit" />
</form>

The second part is handling the file upload in your request handler (above, assumed to answer on /store_mp3). The uploaded file is added to the request object as a FileField object accessible through the Request.POST() coroutine. The two properties we’re interested in are the file and filename and we’ll use those to read file name and content:

import os
import uuid
from pyramid.response import Response

def store_mp3_view(request):

    data = yield from request.POST()

    # ``filename`` contains the name of the file in string format.
    filename = data['mp3'].filename

    # ``input_file`` contains the actual file data which needs to be
    # stored somewhere.

    input_file = data['mp3'].file

    content = input_file.read()

    return aiohttp.web.Response(request, content,
        headers=MultiDict([('CONTENT-DISPOSITION', input-file)])

Request

Request object contains all information about incoming HTTP request.

Every handler accepts request instance as first positional parameter.

Note

You should never create Request instance by hands – aiohttp.web does it for you.

class aiohttp.web.Request[source]
method[source]

HTTP method, read only property.

The value is upper-cased str like "GET", "POST", "PUT" etc.

version[source]

HTTP version of request, read only property.

Returns aiohttp.protocol.HttpVersion instance.

host[source]

HOST header of request, read only property.

Returns str or None if HTTP request has no HOST header.

path_qs[source]

The URL including PATH_INFO and the query string. e.g, /app/blog?id=10

Read only str property.

path[source]

The URL including PATH INFO without the host or scheme. e.g., /app/blog

Read only str property.

query_string[source]

The query string in the URL, e.g., id=10

Read only str property.

GET[source]

A multidict with all the variables in the query string.

Read only MultiDict lazy property.

headers[source]

A case-insensitive multidict with all headers.

Read only CaseInsensitiveMultiDict lazy property.

keep_alive[source]

True if keep-alive connection enabled by HTTP client and protocol version supports it, otherwise False.

Read only bool property.

match_info[source]

Read only property with AbstractMatchInfo instance for result of route resolving.

Note

Exact type of property depends on used router. If app.router is UrlDispatcher the property contains UrlMappingMatchInfo instance.

app[source]

An Application instance used to call request handler, read only property.

cookies[source]

A multidict of all request’s cookies.

Read only MultiDict lazy property.

payload[source]

A FlowControlStreamReader instance, input stream for reading request’s BODY.

Read only property.

content_type

Read only property with content part of Content-Type header.

Returns str like 'text/html'

Note

Returns value is 'application/octet-stream' if no Content-Type header present in HTTP headers according to RFC 2616

charset

Read only property that specifies encoding for request BODY.

The value is parsed from Content-Type HTTP header.

Returns str like 'utf-8' or None if Content-Type has no charset information.

content_length

Read only property that returns length of request BODY.

The value is parsed from Content-Length HTTP header.

Returns int or None if Content-Length is absent.

read()[source]

Read request body, returns bytes object with body content.

The method is a coroutine.

Warning

The method doesn’t store read data internally, subsequent read() call will return empty bytes b''.

text()[source]

Read request body, decode it using charset encoding or UTF-8 if no encoding was specified in MIME-type.

Returns str with body content.

The method is a coroutine.

Warning

The method doesn’t store read data internally, subsequent text() call will return empty string ''.

json(*, loader=json.loads)[source]

Read request body decoded as json.

The method is just a boilerplate coroutine implemented as:

@asyncio.coroutine
def json(self, *, loader=json.loads):
    body = yield from self.text()
    return loader(body)
Parameters:loader (callable) – any callable that accepts str and returns dict with parsed JSON (json.loads() by default).

Warning

The method doesn’t store read data internally, subsequent json() call will raise an exception.

POST()[source]

A coroutine that reads POST parameters from request body.

Returns MultiDict instance filled with parsed data.

If method is not POST, PUT or PATCH or content_type is not empty or application/x-www-form-urlencoded or multipart/form-data returns empty multidict.

Warning

The method does store read data internally, subsequent POST() call will return the same value.

release()[source]

Release request.

Eat unread part of HTTP BODY if present.

The method is a coroutine.

Note

User code may never call release(), all required work will be processed by aiohttp.web internal machinery.

Response

For now aiohttp.web has two classes for HTTP response: StreamResponse and Response.

Usually you need to use the second one. StreamResponse intended for streaming data, Response contains HTTP BODY as attribute and sends own content as single piece with correct Content-Length HTTP header.

For sake of design decisions Response is derived from StreamResponse parent class.

The response supports keep-alive handling out-of-the-box if request supports it.

You can disable keep-alive by force_close() though.

The common case for sending answer from web handler is returning Response instance:

def handler(request):
    return Response(request, "All right!")

StreamResponse

class aiohttp.web.StreamResponse(request. *, status=200, reason=None)[source]

The base class for HTTP response handling.

Contains methods for setting HTTP response headers, cookies, response status code, writing HTTP response BODY and so on.

The most important thing you should to know about response — it is Finite State Machine.

That means you can do any manipulations on headers, cookies and status code only before send_headers() called.

Once you call send_headers() or write() any change of HTTP header part will raise RuntimeError exception.

Any write() call after write_eof() is forbidden also.

Parameters:
  • request (aiohttp.web.Request) – HTTP request object on that the response answers.
  • status (int) – HTTP status code, 200 by default.
  • reason (str) – HTTP reason. If param is None reason will be calculated basing on status parameter. Otherwise pass str with arbitrary status explanation..
request[source]

Read-only property for Request object used for creating the response.

status[source]

Read-only property for HTTP response status code, int.

200 (OK) by default.

reason[source]

Read-only property for HTTP response reason, str.

By default auto calculated basing on status, may be overridden in constructor of StreamResponse.

keep_alive[source]

Read-only property, copy of Request.keep_alive by default.

Can be switched to False by force_close() call.

force_close()[source]

Disable keep_alive for connection. There are no ways to enable it back.

headers[source]

CaseInsensitiveMultiDict instance for outgoing HTTP headers.

cookies[source]

An instance of http.cookies.SimpleCookie for outgoing cookies.

Warning

Direct setting up Set-Cookie header may be overwritten by explicit calls to cookie manipulation.

We are encourage using of cookies and set_cookie(), del_cookie() for cookie manipulations.

Convenient way for setting cookies, allows to point additional cookie properties like max_age in single call.

Parameters:
  • name (str) – cookie name
  • value (str) – cookie value (will be converted to str if value has another type).
  • expries – expiration date (optional)
  • domain (str) – cookie domain (optional)
  • max_age (int) – defines the lifetime of the cookie, in seconds. The delta-seconds value is a decimal non- negative integer. After delta-seconds seconds elapse, the client should discard the cookie. A value of zero means the cookie should be discarded immediately. (optional)
  • path (str) – specifies the subset of URLs to which this cookie applies. (optional)
  • secure (bool) – attribute (with no value) directs the user agent to use only (unspecified) secure means to contact the origin server whenever it sends back this cookie. The user agent (possibly under the user’s control) may determine what level of security it considers appropriate for “secure” cookies. The secure should be considered security advice from the server to the user agent, indicating that it is in the session’s interest to protect the cookie contents. (optional)
  • httponly (bool) – True if the cookie HTTP only (optional)
  • version (int) – a decimal integer, identifies to which version of the state management specification the cookie conforms. (Optional, version=1 by default)

Deletes cookie.

Parameters:
  • name (str) – cookie name
  • domain (str) – optional cookie domain
  • path (str) – optional cookie path
content_length[source]

Content-Length for outgoing response.

content_type[source]

Content part of Content-Type for outgoing response.

charset[source]

Charset aka encoding part of Content-Type for outgoing response.

send_headers()[source]

Send HTTP header. You should not change any header data after calling the method.

write(data)[source]

Send byte-ish data as part of response BODY.

Calls send_headers() if not been called.

Raises TypeError if data is not bytes, bytearray or memoryview instance.

Raises RuntimeError if write_eof() has been called.

write_eof()[source]

A coroutine may be called as mark of finish HTTP response processing.

Internal machinery will call the method at the end of request processing if needed.

After write_eof() call any manipulations with response object are forbidden.

Response

class aiohttp.web.Response(request, body=None, *, status=200, headers=None)[source]

The most usable response class, inherited from StreamResponse.

Accepts body argument for setting HTTP response BODY.

Actual body sending is done in overridden write_eof().

Parameters:
  • request (Request) – HTTP request object used for creation the response.
  • body (bytes) – response’s BODY
  • status (int) – HTTP status code, 200 OK by default.
  • headers (collections.abc.Mapping) – HTTP headers that should be added to response’s ones.
body[source]

Read-write attribute for storing response’s content aka BODY, bytes.

Setting body also recalculates content_length value.

Resetting body (assigning None) set content_length to None also, dropping Content-Length HTTP header.

Application and Router

Application

class aiohttp.web.Application(*, loop=None, router=None, **kwargs)[source]

Application is a synonym for web-server.

The class inherited from dict, so you can use it as registry for arbitrary properies.

To get fully working example you have to make application, register supported url in router and create server socket with make_handler() as protocol factory.

Application contains router instance and list of callbacks that will be called on application finishing. I

Parameters:
  • loop

    event loop used for processing HTTP requests.

    If param is None asyncio.get_event_loop() used for getting default event loop, but we strongly recommend to use explicit loops everywhere.

  • routeraiohttp.abc.AbstractRouter instance, system creates UrlDispatcher by default if router is None.
  • kwargsdict of optional arguments that will be passed to underlying aiohttp.server.ServerHttpProtocol constructor at make_handler() call.
router[source]

Readonly property that returns router instance.

loop[source]

Readonly property that returns event loop.

make_handler()[source]

Creates HTTP protocol for handling requests.

You should never call the method by hands but pass it to create_server() instead as protocol_factory parameter.

Utilities

class aiohttp.web.FileField

A namedtuple() that returned as multidict value by Request.POST() if field is uploaded file.

name

Field name

filename

File name as specified by uploading (client) side.

file

An io.IOBase instance with content of uploaded file.

content_type

MIME type of uploaded file, 'text/plain' by default.

See also

File Uploads

Table Of Contents

Previous topic

HTTP Client

Next topic

Low-level HTTP Server

This Page