# Updated by Siege 2.09, 2001-08-20
# Copyright 2001 by Jeffrey Fulmer
# 
# Siege configuration file -- edit as necessary
# For more information about configuring and running
# this program, visit: http://www.joedog.org

#
# signify verbose mode, true turns on verbose output
# ex: verbose = true|false
#
verbose = false 

#
# default logging status, true turns logging on.
# ex: logging = true|false
#
logging = true

#
# show logfile location.  By default, siege displays the
# logfile location at the end of every run when logging
# You can turn this message off with this directive.
# ex: show-logfile = false
#
show-logfile = true 

#
# HTTP protocol.  Options HTTP/1.1 and HTTP/1.0.
# Some webservers have broken implementation of the
# 1.1 protocol which skews throughput evaluations.
# If you notice some siege clients hanging for
# extended periods of time, change this to HTTP/1.0
# ex: protocol = HTTP/1.1
#     protocol = HTTP/1.0
#
protocol = HTTP/1.1

#
# Connection directive. Options "close" and "keep-alive"
# This directive is only supported by HTTP/1.1 protocol.
# For best throughput use "close" as keep-alive connections
# on dynamic content will hang until the socket times out.
# ex: connection = close
#     connection = keep-alive
connection = close

#
# default number of simulated  concurrent users
# ex: concurrent = 25
#
concurrent = 10

#
# default duration of the siege.  The right hand argument has
# a modifier which specifies the time units, H=hours, M=minutes,
# and S=seconds. If a modifier is not specified, then minutes 
# are assumed.
# ex: time = 50M
#
time = 1m

#
# repetitions.  The length of siege may be specified in client
# reps rather then a time duration.  Instead of specifying a time
# span, you can tell each siege instance to hit the server X number
# of times.  So if you chose 'reps = 20' and you've selected 10 
# concurrent users, then siege will hit the server 200 times.
# ex: reps = 20
#
# reps = 

#
# default delay value, see the siege( 1 ) man page.  
# This value is used for load testing, it is not used 
# for benchmarking.
# ex: delay = 3
#
delay = 1

#
# internet simulation. If true, siege clients will hit
# the URLs in the urls.txt file randomly, thereby simulating
# internet usage.  If false, siege will run through the 
# urls.txt file in order from first to last and back again.
# ex: internet = true
#
internet = true

#
# default benchmarking value, If true, there is NO delay
# between server requests, siege runs as fast as the web
# server and the network will let it.  Set this to false 
# for load testing.
# ex: benchmark = true
# 
benchmark = false

#
# default URLs file, set at configuration time, the default
# file is PREFIX/etc/urls.txt.  So if you configured siege
# with --prefix=/usr/local then the urls.txt file is installed
# int /usr/local/etc/urls.txt.  Use the "file = " directive to
# configure an alternative URLs file.
# ex: file = /export/home/jdfulmer/MYURLS.txt
#
# file =  

#
# default URL, this is a single URL that you want to test. This
# is usually set at the command line with the -u option.  When 
# used, this option overrides the urls.txt (-f FILE/--file=FILE) 
# option. You will HAVE to comment this out for in order to use
# the urls.txt file option.
# ex: url = https://shemp.whoohoo.com/docs/index.jsp
#
# url = 

#
# set the siege User-Agent to identify yourself at the
# host, the default is: JoeDog/1.00 [en] (X11; I; Siege #.##) 
# But that wreaks of corporate techno speak.  Feel free
# to make it more interesting :-)  Since Limey is recovering
# from minor surgery as I write this, I'll dedicate the 
# example to him...
# ex: user-agent = Limey The Bulldog
# 
# user-agent =

#
# WWW-Authenticate username and password.  When siege
# hits a webpage that requires authentication, it will
# send this user name and password to the server.  Note
# this is NOT form based authentication.  You will have
# to construct URLs for that.
#
# ex: username = jdfulmer
#     password = whoohoo
#
# username = 
# password =












