Fetching latest commit…
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
Overview ======== This package provides a WSGI middleware component which automatically scales images according to the ``width`` and ``height`` property in the <img> tag. To configure the middleware, pass in a string for ``secret``; this may be any string internal to the system. You can also set ``filter`` to select the scaling filter. The available filters are ``nearest``, ``bilinear``, ``bicubic`` and ``antialias``. The default is ``antialias``. If you want to change the compression level for JPEG images, then you can set the ``quality`` option to a value between 1 (worst) and 95 (best). The default is 80. By default all image URLs are rewritten. With ``limit_to_application_url`` you can limit the rewriting to relative URLs and absolute URLs below the application URL. A minimal cache implementation is available with the ``cache`` parameter. It should be the path to a directory where generated images will be saved. This is a very simplistic approach that does not use any possibly related HTTP header at all: ``Last-Modified``, ``Expires``, etc. The only way to refresh or empty the cache is to delete the files. This feature is disabled by default. Usage ----- The middleware operates in two phases, on HTML documents and images respectively. When processing HTML documents, it looks for image tags in the document soup:: <img src="some_image.png" width="640" height="480" /> In the case it finds such an image element, it rewrites the URL to include scaling information which the middleware will read when the image is served through it. The image will be proportionally scaled, so it fits into the given size. If you only set one of width or height, then the image will only be limited to that, but still proportionally scaled. This effectively means that application developers needn't worry about image scaling; simply put the desired size in the HTML document. Note that this middleware is protected from DoS attacks (which is important for any middleware that does significant processing) by signing all URLs with an SHA digest signature. Contributing ------------ The development of repoze.bitblt happens at github: https://github.com/repoze/repoze.bitblt Credits ------- * Malthe Borch <email@example.com> * Stefan Eletzhofer <firstname.lastname@example.org> * Jeroen Vloothuis <email@example.com> * Florian Schulze <firstname.lastname@example.org>