upload module 2.0.10

[nginx.mailinglist]

good stuff! appreciated
just a quick question, how are uploads with no name or unicode handled? are
any special characters filtered for safety?


On Sun, Aug 30, 2009 at 10:47 AM, Valery Kholodkov <
valery+nginxen at grid.net.ru <valery%2Bnginxen at grid.net.ru>> wrote:

>
> Changes in version 2.0.10:
>  * Change: compatibility with nginx API 0.8.11;
>  * Fixed bug: Prevent module from registering store path if no upload
> location was configured;
>  * Fixed bug: upload corruption in case of short body + keepalive. Thanks
> to Dmitry Dedukhin;
>  * Change: Return error 415 instead of 400 if request content type is not
> multipart/form-data.
>
> Please note, that 2.1.x is a development branch. To continue using the most
> stable version of upload module please stay with 2.0.x branch until further
> notice.
>
> Also please note that it is now possible to route requests of types other
> that multipart/form-data to something which understands it. Example:
>
> location = /upload {
>    upload_pass @blah;
>
>    [...]
>
>    error_page 415 = @non_multipart_formdata;
> }
>
> location @non_multipart_formdata {
>    fastcgi_pass ...;
> }
>
>
> Please see this page for details:
> http://www.grid.net.ru/nginx/upload.en.html
>
> --
> Best regards,
> Valery Kholodkov
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20090830/7c52077a/attachment.html>