OpenLiteSpeed 1.2.4 and requests

182 views
Skip to first unread message

lsmichael

unread,
Aug 22, 2013, 5:45:12 PM8/22/13
to openlitespee...@googlegroups.com
Howdy,

We just put out 1.2.4 — it improves OCSP stapling and allows autoindexing even on vhosts where scripts are disabled. We're hard at work on an API for people to develop add-ons and hope to have it ready in the next month or so.

What else would you like to see? Where does OpenLiteSpeed fall short of your expectations? (Except that it doesn't read .htaccess files or work with control panels.) What can we do to make you tell your friends about it?

George Liu

unread,
Aug 22, 2013, 10:34:38 PM8/22/13
to openlitespee...@googlegroups.com
Hi Michael been a while since i played with OpenLiteSpeed :)

With 1.2.4 and on first admin console log in i see one error logged

2013-08-23 12:22:03.268 ERROR [config:admin:listener:adminListener] SPDY can't be enabled [failed to set to 3].

normal  ? ignore ?

I installed via git repository on CentOS 6.4 using this one liner command in SSH telnet

echo; echo "Install OpenLiteSpeed via git:"; read -ep "Where do you want to download OpenLiteSpeed source files to ? i.e. /usr/local/src: " DIR; echo; echo "Installing yum packages required..."; echo; yum -q -y install git gcc gcc-c++ make autoconf glibc; yum -q -y install pcre-devel expat-devel openssl-devel geoip-devel zlib-devel; echo; echo "yum packages installed"; cd $DIR; git clone https://github.com/litespeedtech/openlitespeed.git; cd ${DIR}/openlitespeed; TAG=$(git tag -l | tail -1); git checkout $TAG;./configure; make && make install; echo; echo "Web Admin Console: https://$(uname -n):7080"; echo "Admin: admin Pass: 123456"; echo; echo "Default sample site: http://$(uname -n):8088"; echo

So no SPDY configured via source install.

Speaking of SPDY http://open.litespeedtech.com/mediawiki/index.php/Help:Install:OpenLiteSpeed_with_SPDY_Installation_Notes is it at all possible to make it similar to Nginx, only requiring the openssl 1.0.1e tar ball be extracted and not actually installed ? Then the install process does it's thing with openssl 1.0.1e ? Nginx makes this simply as all you do is extract openssl 1.0.1e tarball and don't need to install it :)

cheers

George Liu

unread,
Aug 22, 2013, 10:49:30 PM8/22/13
to openlitespee...@googlegroups.com
Fixed my one liner shell install with proper branch check out for anyone using it

echo; echo "Install OpenLiteSpeed via git:"; read -ep "Where do you want to download OpenLiteSpeed source files to ? i.e. /usr/local/src: " DIR; echo; echo "Installing yum packages required..."; echo; yum -q -y install git gcc gcc-c++ make autoconf glibc; yum -q -y install pcre-devel expat-devel openssl-devel geoip-devel zlib-devel; echo; echo "yum packages installed"; cd $DIR; git clone https://github.com/litespeedtech/openlitespeed.git; cd ${DIR}/openlitespeed; BRANCH=$(git branch -r | tail -1); git checkout -t $BRANCH;./configure; make && make install; echo; echo "Web Admin Console: https://$(uname -n):7080"; echo "Admin: admin Pass: 123456"; echo; echo "Default sample site: http://$(uname -n):8088"; echo

lsmichael

unread,
Aug 23, 2013, 5:59:44 PM8/23/13
to openlitespee...@googlegroups.com
Howdy George,

Good to see you back. First, the error: Yes, that's normal. That just means that SPDY can't be enabled for whatever reason, probably because you don't have a high enough version of OpenSSL.

Also, did you put your updated one liner on the repository thread, too? Wouldn't want someone to get tripped up.

And, about using SPDY without actually installing OpenSSL 1.0.1 — We can do that. Not sure it's top priority, but it shouldn't be hard to do. We'll try to have it in the next release.

Cheers,

Michael

George Liu

unread,
Aug 23, 2013, 7:31:46 PM8/23/13
to openlitespee...@googlegroups.com
Awesome would be great to have SPDY setup made easier by just having to extract openssl 1.0.1e tarball and pointing to it :)

Yes, the one linger is in repository thread too :)

MikeB

unread,
Sep 3, 2013, 3:15:20 AM9/3/13
to openlitespee...@googlegroups.com
Can you please add an option to send a header for clients connecting on port 80 when SPDY is available?

Alternate-Protocol: 443:npn-spdy/3

lsmichael

unread,
Sep 10, 2013, 6:40:17 PM9/10/13
to openlitespee...@googlegroups.com
It's being worked on as we speak.
Reply all
Reply to author
Forward
0 new messages