[Rabbit-dev] Current changelog for 4.12 and some notes about http/2.0

[Robert Olofsson]

Hello!

Rabbit is not dead yet :-)

Current changelog for 4.12 looks like:

version 4.12 (20xx-yy-zz) Only pass a proxy-authentication token if it
is actually set to something. Made it possible to configure
tcp_no_delay on or off. Do not close connections when a filter
sends back an unauthorized header. Handle some utf-8 aliases as
utf-8. Try to read off resource data when a request is
blocked. Upgraded rnio to 1.3-pre.

A different question is what to do about the http/2.0 specification
that is currently being discussed by ietf. Currently it looks hard
to make rabbit do anything useful with http/2.0. but from the mailing
list it seems they are going to talk about proxies in the near future.
So we will see what happen with rabbit and http/2.0.

/robo

[Luis Soltero]

Absolutely rabbit is not dead...

We have been using it and comparing it with mod_pagespeed running in proxy mode. Our results continue to show that
rabbit works much better for us than mod_pagespeed.

Having said that we are experimenting

end user --> rabbit --> http/mod_pagespeed proxy --> internet.

So far this works quite well. Pages on the internet are optimized before they are fed to rabbit for heavy filtering,
caching, and image resampling.

We are concerned about http 2.0. Please keep us posted on issues/repercussions of this new technology.

--luis

Post by Robert Olofsson
Hello!
Rabbit is not dead yet :-)
version 4.12 (20xx-yy-zz) Only pass a proxy-authentication token if it
is actually set to something. Made it possible to configure
tcp_no_delay on or off. Do not close connections when a filter
sends back an unauthorized header. Handle some utf-8 aliases as
utf-8. Try to read off resource data when a request is
blocked. Upgraded rnio to 1.3-pre.
A different question is what to do about the http/2.0 specification
that is currently being discussed by ietf. Currently it looks hard
to make rabbit do anything useful with http/2.0. but from the mailing
list it seems they are going to talk about proxies in the near future.
So we will see what happen with rabbit and http/2.0.
/robo
_______________________________________________
Rabbit-dev mailing list
Rabbit-dev at khelekore.org
http://khelekore.org/cgi-bin/mailman/listinfo/rabbit-dev

--
Luis Soltero, Ph.D., MCS
Director of Software Development, CTO
Global Marine Networks, LLC
StarPilot, LLC
Tel: [phone]
Fax: [phone]
E-Mail: lsoltero at globalmarinenet.net
Web: http://www.globalmarinenet.net
Web: http://www.redportglobal.com
Web: http://www.starpilotllc.com

[Samat K Jain]

Post by Robert Olofsson
A different question is what to do about the http/2.0 specification
that is currently being discussed by ietf. Currently it looks hard
to make rabbit do anything useful with http/2.0. but from the mailing
list it seems they are going to talk about proxies in the near future.
So we will see what happen with rabbit and http/2.0.

If we're thinking about http/2.0-related feature requests


SPDY support for RabbIT. That is, the ability for a browser to connect
to RabbIT over SSL (supported in Chrome, just landed in Firefox[1]) and
all requests be sent pipelined via SPDY from RabbIT back to the Web browser.

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=378637