79 lines
2.6 KiB
Plaintext
79 lines
2.6 KiB
Plaintext
|
# Updated by Siege %_VERSION%, %_DATE%
|
||
|
|
# Copyright 2000-2016 by %_AUTHOR%
|
||
|
|
#
|
||
|
|
# Siege configuration file -- edit as necessary
|
||
|
|
# For more information about configuring and running this program,
|
||
|
|
# visit: http://www.joedog.org/
|
||
|
|
|
||
|
|
#
|
||
|
|
#
|
||
|
|
# Verbose mode: With this feature enabled, siege will print the
|
||
|
|
# result of each transaction to stdout. (Enabled by default)
|
||
|
|
#
|
||
|
|
# ex: verbose = true|false
|
||
|
|
#
|
||
|
|
verbose = true
|
||
|
|
|
||
|
|
#
|
||
|
|
# Color mode: This option works in conjunction with verbose mode.
|
||
|
|
# It tells siege whether or not it should display its output in
|
||
|
|
# color-coded output. (Enabled by default)
|
||
|
|
#
|
||
|
|
# ex: color = on | off
|
||
|
|
#
|
||
|
|
color = on
|
||
|
|
|
||
|
|
#
|
||
|
|
# Cache revalidation. Siege supports cache revalidation for both ETag
|
||
|
|
# and Last-modified headers. If a copy is still fresh, the server
|
||
|
|
# responds with 304. While this feature is required for HTTP/1.1, it
|
||
|
|
# may not be welcomed for load testing. We allow you to breach the
|
||
|
|
# protocol and turn off caching
|
||
|
|
#
|
||
|
|
# HTTP/1.1 200 0.00 secs: 2326 bytes ==> /apache_pb.gif
|
||
|
|
# HTTP/1.1 304 0.00 secs: 0 bytes ==> /apache_pb.gif
|
||
|
|
# HTTP/1.1 304 0.00 secs: 0 bytes ==> /apache_pb.gif
|
||
|
|
#
|
||
|
|
# Siege also supports Cache-control headers. Consider this server
|
||
|
|
# response: Cache-Control: max-age=3
|
||
|
|
# That tells siege to cache the file for three seconds. While it
|
||
|
|
# doesn't actually store the file, it will logically grab it from
|
||
|
|
# its cache. In verbose output, it designates a cached resource
|
||
|
|
# with (c):
|
||
|
|
#
|
||
|
|
# HTTP/1.1 200 0.25 secs: 159 bytes ==> GET /expires/
|
||
|
|
# HTTP/1.1 200 1.48 secs: 498419 bytes ==> GET /expires/Otter_in_Southwold.jpg
|
||
|
|
# HTTP/1.1 200 0.24 secs: 159 bytes ==> GET /expires/
|
||
|
|
# HTTP/1.1 200(C) 0.00 secs: 0 bytes ==> GET /expires/Otter_in_Southwold.jpg
|
||
|
|
#
|
||
|
|
# NOTE: with color enabled, cached URLs appear in green
|
||
|
|
#
|
||
|
|
# ex: cache = true
|
||
|
|
#
|
||
|
|
cache = true
|
||
|
|
|
||
|
|
#
|
||
|
|
# Cookie support: by default siege accepts cookies. This directive is
|
||
|
|
# available to disable that support. Set cookies to 'false' to refuse
|
||
|
|
# cookies. Set it to 'true' to accept them. The default value is true.
|
||
|
|
# If you want to maintain state with the server, then this MUST be set
|
||
|
|
# to true.
|
||
|
|
#
|
||
|
|
# ex: cookies = false
|
||
|
|
#
|
||
|
|
cookies = true
|
||
|
|
|
||
|
|
#
|
||
|
|
# Failures: This is the number of total connection failures allowed
|
||
|
|
# before siege aborts. Connection failures (timeouts, socket failures,
|
||
|
|
# etc.) are combined with 400 and 500 level errors in the final stats,
|
||
|
|
# but those errors do not count against the abort total. If you set
|
||
|
|
# this total to 10, then siege will abort after ten socket timeouts,
|
||
|
|
# but it will NOT abort after ten 404s. This is designed to prevent a
|
||
|
|
# run-away mess on an unattended siege.
|
||
|
|
#
|
||
|
|
# The default value is 1024
|
||
|
|
#
|
||
|
|
# ex: failures = 50
|
||
|
|
#
|
||
|
|
failures = -1
|