Unsupported protocol

[Robert]

I've recently downloaded a copy of siege and setup a real quick test
against one of our internal sites. It worked fantastically well. The
site tested used the http protocol. However, when I attempted to use
siege against a site supporting the https protocol, I get an
'unsupported protocol' message. My test environment is as follows:

Machine information:
Linux TerminalVelocity 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12
05:23:09 UTC 2010 i686 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu 9.10
Release: 9.10
Codename: karmic

I built siege with the following command: ./configure --with-ssl=/usr/
bin/openssl. So, I'm pretty sure it has SSL support. Unfortunately,
when I execute the following command

siege -g http://hostname.net/pnp/login

I get

GET /pnp/login HTTP/1.1
Host: hostname.net
Accept: */*
Accept-Encoding: gzip
User-Agent: JoeDog/1.00 [en] (X11; I; Siege 2.69)
Connection: close


HTTP/1.1 302 Moved Temporarily
Server: Apache-Coyote/1.1
Cache-Control: private
Expires: Wed, 31 Dec 1969 16:00:00 PST
Location: https://hostname.net/pnp/login
Content-Length: 0
Date: Tue, 27 Apr 2010 19:43:50 GMT
Connection: close

warning: unsupported protocol: Operation now in progress
Segmentation fault

Any help/guidance as to where I may have gone wrong would be
appreciated. Thanks.


Regards,
Robert

[Jeff]

On Apr 27, 5:46 pm, Robert <restag...@gmail.com> wrote:
> I've recently downloaded a copy of siege and setup a real quick test
> against one of our internal sites.  It worked fantastically well.  The
> site tested used the http protocol.  However, when I attempted to use
> siege against a site supporting the https protocol, I get an
> 'unsupported protocol' message.  My test environment is as follows:
>
> Machine information:
> Linux TerminalVelocity 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12
> 05:23:09 UTC 2010 i686 GNU/Linux
>
> Distributor ID: Ubuntu
> Description:    Ubuntu 9.10
> Release:        9.10
> Codename:       karmic
>
> I built siege with the following command: ./configure --with-ssl=/usr/
> bin/openssl.  So, I'm pretty sure it has SSL support.  Unfortunately,
> when I execute the following command
>

> siege -ghttp://hostname.net/pnp/login

>
> I get
>
> GET /pnp/login HTTP/1.1
> Host: hostname.net
> Accept: */*
> Accept-Encoding: gzip
> User-Agent: JoeDog/1.00 [en] (X11; I; Siege 2.69)
> Connection: close
>
> HTTP/1.1 302 Moved Temporarily
> Server: Apache-Coyote/1.1
> Cache-Control: private
> Expires: Wed, 31 Dec 1969 16:00:00 PST
> Location:https://hostname.net/pnp/login
> Content-Length: 0
> Date: Tue, 27 Apr 2010 19:43:50 GMT
> Connection: close
>
> warning: unsupported protocol: Operation now in progress
> Segmentation fault
>
> Any help/guidance as to where I may have gone wrong would be
> appreciated.  Thanks.
>

Robert,

The segmentation fault is troublesome. I'll look into that.

It looks like you've compiled it by pointing it to the openssl binary.
The argument requires a directory in which openssl is installed. This
is for people who install openssl outside LIB_PATH. In other words, if
you compiled openssl with --prefix=/usr/local/ssl then you would
compile siege with --use-ssl=/usr/local/ssl

In your case, I suspect you won't need --use-ssl ; configure will find
the library automagically.

Cheers,
Jeff

[Robert]

Jeff,

I appreciate the quick response. Thinking back (it was only 2 days
ago :-) ) to when I installed seige, I recall that I did not encounter
any warnings or errors, so I suspect that configure automagically
located the ssl library. Once you've had a chance to look into this
issue, please let me know what your findings are. We are looking into
the possibility of using siege within our test environment. Thanks.

[Jeff]

On Apr 28, 10:15 am, Robert <restag...@gmail.com> wrote:
> Jeff,
>
> I appreciate the quick response.  Thinking back (it was only 2 days
> ago :-) ) to when I installed seige, I recall that I did not encounter
> any warnings or errors, so I suspect that configure automagically
> located the ssl library.  Once you've had a chance to look into this
> issue, please let me know what your findings are.  We are looking into
> the possibility of using siege within our test environment.  Thanks.
>

configure is setup to detect the openssl headers. If it doesn't locate
the header, it will compile for http only. Since you're using Ubuntu,
you might need to add another package and try to compile again. You
probably need a package like openssl-devel which includes the
libraries and header files.

When you run configure, look for this section of output:
checking for ssl support... yes
checking off/include/openssl/opensslv.h usability... no
checking off/include/openssl/opensslv.h presence... no
checking for off/include/openssl/opensslv.h... no
checking /usr/include/openssl/opensslv.h usability... yes
checking /usr/include/openssl/opensslv.h presence... yes
checking for /usr/include/openssl/opensslv.h... yes
checking for OpenSSL version... >= 0.9.8 (appropriate flag set)

If everything after "checking for ssl support" is "no", then you need
to fix your environment.

[Robert Stagner]

Jeff,

I think I'm getting closer to a working environment.  As you pointed out earlier, the ssl libraries were not installed -- I received a "no" on everything after "checking for ssl support... yes".  So, I went ahead and installed the libssl-dev package from the Ubuntu repository.  Once that was done, I uninstalled Siege, and then ran ./configure again.  The output from the configure operation was

checking for ssl support... yes                                               

checking off/include/openssl/opensslv.h usability... no                       

checking off/include/openssl/opensslv.h presence... no                        

checking for off/include/openssl/opensslv.h... no                             

checking /usr/include/openssl/opensslv.h usability... yes                     

checking /usr/include/openssl/opensslv.h presence... yes                      

checking for /usr/include/openssl/opensslv.h... yes                           

checking for OpenSSL version... >= 0.9.8 (appropriate flag set)               

I then went ahead and installed Siege, hoping for the best.  Unfortunately, when I executed the following

siege -g https://somehost.name.net/pnp/login

I got 

warning: unsupported protocol

[done]

I think it has to do with the fact that I'm still seeing

checking off/include/openssl/opensslv.h usability... no                       

checking off/include/openssl/opensslv.h presence... no                        

checking for off/include/openssl/opensslv.h... no                             

when I run configure.  However, I'm not sure how to proceed with this, considering I've installed the libssl-dev package.  Any help would be truly appreciated.

Regards,

Robert

--
Regards,
Robert

[Jeff]

On Apr 29, 7:26 pm, Robert Stagner <restag...@gmail.com> wrote:
> Jeff,
>
> I think I'm getting closer to a working environment.  As you pointed out
> earlier, the ssl libraries were not installed -- I received a "no" on
> everything after "checking for ssl support... yes".  So, I went ahead and
> installed the libssl-dev package from the Ubuntu repository.  Once that was
> done, I uninstalled Siege, and then ran ./configure again.  The output from
> the configure operation was
>
> checking for ssl support... yes
>
> checking off/include/openssl/opensslv.h usability... no
>
> checking off/include/openssl/opensslv.h presence... no
>
> checking for off/include/openssl/opensslv.h... no
>
> checking /usr/include/openssl/opensslv.h usability... yes
>
> checking /usr/include/openssl/opensslv.h presence... yes
>
> checking for /usr/include/openssl/opensslv.h... yes
>
> checking for OpenSSL version... >= 0.9.8 (appropriate flag set)
>
> I then went ahead and installed Siege, hoping for the best.  Unfortunately,
> when I executed the following
>

> siege -ghttps://somehost.name.net/pnp/login

>
> I got
>
> warning: unsupported protocol
> [done]
>
> I think it has to do with the fact that I'm still seeing
>
> checking off/include/openssl/opensslv.h usability... no
>
> checking off/include/openssl/opensslv.h presence... no
>
> checking for off/include/openssl/opensslv.h... no
>
> when I run configure.  However, I'm not sure how to proceed with this,
> considering I've installed the libssl-dev package.  Any help would be truly
> appreciated.
>
> Regards,
> Robert
>

Can you "find / -name ">

can you: find / -name "opensslv.h"

[Robert Stagner]

Executing find / -name "opensslv.h" resulted in 0 matches.

--
Regards,
Robert

[Jeff]

On Apr 30, 12:36 am, Robert Stagner <restag...@gmail.com> wrote:
> Executing find / -name "opensslv.h" resulted in 0 matches.
>

Robert,
Here's what I have on ubuntu:

Bully $ dpkg --get-selections|grep openssl
openssl install
openssl-blacklist install
python-openssl install
Bully $ ls /usr/include/openssl/opensslv.h
/usr/include/openssl/opensslv.h

Jeff

[Robert Stagner]

Jeff,

Ok, so here is what it returns for me

$ dpkg --get-selections | grep openssl
openssl                                         install

$ ls /usr/include/openssl/opensslv.h
/usr/include/openssl/opensslv.h

Looks like I'm missing two packages.  However, it appears that I have the opensslv.h.  So, probably no need to install the openssl-blacklist or python packages, correct?  How can I get Siege to recognize the opensslv.h file during the configuration process?

I feel like I'm only 'inches' away from having this up and running.

--
Regards,
Robert

[Robert Stagner]

Jeff,

Is there anything else I can do to somehow get this up and running?

On Apr 30, 2010 3:02 AM, "Jeff" <joes...@gmail.com> wrote:

On Apr 30, 12:36 am, Robert Stagner <restag...@gmail.com> wrote:

> Executing find / -name "opensslv....

[Jeff]

On May 1, 4:15 pm, Robert Stagner <restag...@gmail.com> wrote:
> Jeff,
>
> Is there anything else I can do to somehow get this up and running?

Robert,

I'm not sure what you'd like to hear. In order to do https, siege
requires a functional openssl library to which it can link against.
Without a functional library, there's not much we can do. It looks
like you have the openssl binary but you don't have the library.

If Ubuntu packages are confusing, you could always download openssl
and compile it from source. So you don't walk on your existing openssl
stuff, you could set the prefix to /usr/local/ssl. (--prefix=/usr/
local/ssl) Then when you compile siege, use that location. ./configure
--prefix=/home/robert --with-ssl=/usr/local/ssl

Jeff

[Christof Damian]

there also seems to be a siege package for ubuntu, which does seem to
support ssl. Might be easier to use that:
http://packages.ubuntu.com/karmic/siege

[Robert Stagner]

Jeff,

Thanks for the additional information and your time. I'll have a look at possibly downloading and installing openssl from source.  I'll also have a look at Christof's recommendation regarding downloading and installing the siege package for Ubuntu.

Thanks!!

--
Regards,
Robert

[Rasmus Luckow-Nielsen]

Thank you for this thread! I had exactly the same problem with 2.70b3, and the SSL was the problem. Solved it on my ubuntu box by manually compiling the openssl source and then recompiling siege. Great!