venkatbo wrote:
> So, it looks like, if I want HTTP1.1 support
> (and not use the bulky Apache) lighttpd
> (proxy to TG/CP) is pretty much the best bet
It's as good as any. What specific features of HTTP/1.1 are
you interested in?
> From what I've read so far, CP's webserver only
> supports HTTP1.0. Would funneling all the 1.1reqs
> (coming into lighttpd) as 1.0 reqs to CP,
> negatively affect thruput to a significant extent?
Nope.
> Also, I'm presuming if I want to enable HTTPS
> in lighttp (via openssl), everything downstream
> (from lighttpd) will fucntion unchaged...
That's correct. The CherryPy framework handles HTTP/1.1
just fine--it's only the builtin server that is missing a
couple of 1.1 features (like chunked transfer-codings). If
you use CP with a 1.1-compliant server, it will happily
generate 1.1-compliant headers 'n such.
Robert Brewer
System Architect
Amor Ministries
fumanchu amor.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-users googlegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---
|