> I've just pushed *Sinatra 1.3.3* to rubygems.org. This is a bug fix
> release.

> From the change log:

>    -  Improved documentation.
>    -  No longer modify the load path.
>    -  When keeping a stream open, set up callback/errback correctly to
>    deal with clients closing the connection.
>    -  Fix bug where having a query param and a URL param by the same name
>    would concatenate the two values.
>    -  Prevent duplicated log output when application is already wrapped
>    in a `Rack::CommonLogger`.
>    -  Fix issue where `Rack::Link` and Rails were preventing indefinite
>    streaming.
>    -  No longer cause warnings when running Ruby with `-w`.
>    -  HEAD requests on static files no longer report a Content-Length of
>    0, but instead the proper length.
>    -  When protecting against CSRF attacks, drop the session instead of
>    refusing the request.

> Special thanks for helping with this release go out to Matt Wildig,
> michelc, Gabriel Andretta, burningTyger, Sukjoon Kim, Mat Schaffer, Nikica
> Jokić, Jordan Moncharmont, Michael Hutchinson, Melvin Lammerts, Nick
> Sieger, Alex MacCaw, Kashyap, Michael Klishin, GordonDiggs and Peter Powell.

> Enjoy!
> Konstantin

> --
> You received this message because you are subscribed to the Google Groups
> "sinatrarb" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/sinatrarb/-/4h20rh4JEZEJ.
> To post to this group, send email to sinatrarb@googlegroups.com.
> To unsubscribe from this group, send email to
> sinatrarb+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/sinatrarb?hl=en.

On Sunday, August 19, 2012 3:07:32 PM UTC+2, k.h...@finn.de wrote:

> I've just pushed *Sinatra 1.3.3* to rubygems.org. This is a bug fix
> release.

> From the change log:

>    -  Improved documentation.
>    -  No longer modify the load path.
>    -  When keeping a stream open, set up callback/errback correctly to
>    deal with clients closing the connection.
>    -  Fix bug where having a query param and a URL param by the same name
>    would concatenate the two values.
>    -  Prevent duplicated log output when application is already wrapped
>    in a `Rack::CommonLogger`.
>    -  Fix issue where `Rack::Link` and Rails were preventing indefinite
>    streaming.
>    -  No longer cause warnings when running Ruby with `-w`.
>    -  HEAD requests on static files no longer report a Content-Length of
>    0, but instead the proper length.
>    -  When protecting against CSRF attacks, drop the session instead of
>    refusing the request.

> Special thanks for helping with this release go out to Matt Wildig,
> michelc, Gabriel Andretta, burningTyger, Sukjoon Kim, Mat Schaffer, Nikica
> Jokić, Jordan Moncharmont, Michael Hutchinson, Melvin Lammerts, Nick
> Sieger, Alex MacCaw, Kashyap, Michael Klishin, GordonDiggs and Peter Powell.

> Enjoy!
> Konstantin

>  No longer cause warnings when running Ruby with `-w`.

On Sun, Aug 19, 2012 at 9:07 AM,  <k.ha...@finn.de> wrote:
> I've just pushed Sinatra 1.3.3 to rubygems.org. This is a bug fix release.

> From the change log:

>  Improved documentation.
>  No longer modify the load path.
>  When keeping a stream open, set up callback/errback correctly to deal with
> clients closing the connection.
>  Fix bug where having a query param and a URL param by the same name would
> concatenate the two values.
>  Prevent duplicated log output when application is already wrapped in a
> `Rack::CommonLogger`.
>  Fix issue where `Rack::Link` and Rails were preventing indefinite
> streaming.
>  No longer cause warnings when running Ruby with `-w`.
>  HEAD requests on static files no longer report a Content-Length of 0, but
> instead the proper length.
>  When protecting against CSRF attacks, drop the session instead of refusing
> the request.

> Special thanks for helping with this release go out to Matt Wildig, michelc,
> Gabriel Andretta, burningTyger, Sukjoon Kim, Mat Schaffer, Nikica Jokić,
> Jordan Moncharmont, Michael Hutchinson, Melvin Lammerts, Nick Sieger, Alex
> MacCaw, Kashyap, Michael Klishin, GordonDiggs and Peter Powell.

> Enjoy!
> Konstantin

> --
> You received this message because you are subscribed to the Google Groups
> "sinatrarb" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/sinatrarb/-/4h20rh4JEZEJ.
> To post to this group, send email to sinatrarb@googlegroups.com.
> To unsubscribe from this group, send email to
> sinatrarb+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/sinatrarb?hl=en.

On Sunday, 19 August 2012 21:07:32 UTC+8, k.h...@finn.de wrote:

> I've just pushed *Sinatra 1.3.3* to rubygems.org. This is a bug fix
> release.

> From the change log:

>    -  Improved documentation.
>    -  No longer modify the load path.
>    -  When keeping a stream open, set up callback/errback correctly to
>    deal with clients closing the connection.
>    -  Fix bug where having a query param and a URL param by the same name
>    would concatenate the two values.
>    -  Prevent duplicated log output when application is already wrapped
>    in a `Rack::CommonLogger`.
>    -  Fix issue where `Rack::Link` and Rails were preventing indefinite
>    streaming.
>    -  No longer cause warnings when running Ruby with `-w`.
>    -  HEAD requests on static files no longer report a Content-Length of
>    0, but instead the proper length.
>    -  When protecting against CSRF attacks, drop the session instead of
>    refusing the request.

> Special thanks for helping with this release go out to Matt Wildig,
> michelc, Gabriel Andretta, burningTyger, Sukjoon Kim, Mat Schaffer, Nikica
> Jokić, Jordan Moncharmont, Michael Hutchinson, Melvin Lammerts, Nick
> Sieger, Alex MacCaw, Kashyap, Michael Klishin, GordonDiggs and Peter Powell.

> Enjoy!
> Konstantin

On Fri, Aug 24, 2012 at 04:40:31AM -0700, Jason Garber wrote:
> Very nice! Also, it's been 11 months since a sinatra-contrib release. Might
> want to think about pushing that as well.