[httperf] Request Headers

Arlitt, Martin martin.arlitt at hp.com
Thu Nov 27 07:31:48 PST 2008


I just wanted to make sure I'm using the same copy.

I don't know why we are seeing different things.  My guess at this point is (perhaps) our systems are picking up different getopt_long functions, and for some reason your's isn't working in the expected way.  But since I can't replicate the problem you are seeing, you'll have to dig into that yourself.

Sorry I can't be of more help.  If you feel like exploring, I'd start by looking at what getopt_long returns within httperf.c for the simplified command line (or why param.additional_header doesn't get set).

Martin

> -----Original Message-----
> From: Delano Mandelbaum [mailto:delano at solutious.com]
> Sent: Thursday, November 27, 2008 7:15 AM
> To: Arlitt, Martin
> Cc: httperf at napali.hpl.hp.com
> Subject: Re: [httperf] Request Headers
>
> Nope, I'm using the httperf-0.9.0.tar.gz release and haven't made any
> changes
>
> $ md5sum src/httperf.c
> 45b92299bdc95fe3e8b8a977a0abbb3d  src/httperf.c
>
>
>
> On Thu, Nov 27, 2008 at 4:12 PM, Arlitt, Martin <martin.arlitt at hp.com>
> wrote:
> > Have you made any modifications to httperf.c?  if not, what is the
> md5sum?
> >
> >> -----Original Message-----
> >> From: Delano Mandelbaum [mailto:delano at solutious.com]
> >> Sent: Thursday, November 27, 2008 7:07 AM
> >> To: Arlitt, Martin
> >> Cc: httperf at napali.hpl.hp.com
> >> Subject: Re: [httperf] Request Headers
> >>
> >> Looks the same:
> >>
> >> $ httperf --server=tp1 −−add−header="X-Header: text\n" --print-request
> >> httperf --print-request --client=0/1 --server=tp1 --port=80 --uri=/
> >> --send-buffer=4096 --recv-buffer=16384 --num-conns=1 --num-calls=1
> >> SH0:GET / HTTP/1.1
> >> SH0:User-Agent: httperf/0.9.0
> >> SH0:Host: tp1
> >> SH0:
> >> SS0: header 56 content 0
> >> Maximum connect burst length: 0
> >>
> >> Total: connections 1 requests 1 replies 1 test-duration 0.001 s
> >>
> >>
> >> I'm running Debian 5.0 (Lenny). Here's the output from uname -a:
> >> Linux domU-12-31-39-02-F4-A7 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15
> >> 12:39:36 EST 2008 i686 GNU/Linux
> >>
> >> Delano
> >>
> >>
> >> On Thu, Nov 27, 2008 at 3:55 PM, Arlitt, Martin <martin.arlitt at hp.com>
> >> wrote:
> >> > First thing I suggest trying is dropping all of the extra options
> (i.e.,
> >> just keep --server, --add-header, and --print-request).
> >> >
> >> > Also, what platform are you running this on?
> >> >
> >> >> -----Original Message-----
> >> >> From: Delano Mandelbaum [mailto:delano at solutious.com]
> >> >> Sent: Thursday, November 27, 2008 6:49 AM
> >> >> To: Arlitt, Martin
> >> >> Cc: httperf at napali.hpl.hp.com
> >> >> Subject: Re: [httperf] Request Headers
> >> >>
> >> >> Hmm, that's curious. Here's the output when I run the command:
> >> >>
> >> >> $ httperf --server=tp1 --uri=/small.html --num-conns=1 --rate=0
> >> >> --timeout=30 --think-timeout=0 −−add−header="X-Header: test\n"
> >> >> --print-request
> >> >> httperf --print-request --timeout=30 --client=0/1 --server=tp1
> >> >> --port=80 --uri=/small.html --send-buffer=4096 --recv-buffer=16384
> >> >> --num-conns=1 --num-calls=1
> >> >> SH0:GET /small.html HTTP/1.1
> >> >> SH0:User-Agent: httperf/0.9.0
> >> >> SH0:Host: tp1
> >> >> SH0:
> >> >> SS0: header 70 content 0
> >> >> Maximum connect burst length: 0
> >> >>
> >> >> Total: connections 1 requests 1 replies 1 test-duration 0.001 s
> >> >>
> >> >>
> >> >> Actually, I just noticed that httperf does not echo back the
> >> >> add-header parameter in the first line of my output. What does that
> >> >> mean?
> >> >>
> >> >> Delano
> >> >>
> >> >>
> >> >> On Thu, Nov 27, 2008 at 3:33 PM, Arlitt, Martin
> <martin.arlitt at hp.com>
> >> >> wrote:
> >> >> > Hi Delano
> >> >> >
> >> >> > I'm not sure why it's not working for you; it seems to work for
> me:
> >> >> >
> >> >> > $ ./httperf --server=mysvr --print-request --add-header="X-Header:
> >> >> test\n"
> >> >> > httperf --print-request --client=0/1 --server=mysvr --port=80 --
> uri=/
> >> --
> >> >> send-buffer=4096 --recv-buffer=16384 --add-header='X-Header: test\n'
> --
> >> >> num-conns=1 --num-calls=1
> >> >> > SH0:GET / HTTP/1.1
> >> >> > SH0:User-Agent: httperf/0.9.0
> >> >> > SH0:Host: mysvr
> >> >> > SH0:X-Header: test
> >> >> > SH0:
> >> >> > SS0: header 75 content 0
> >> >> > Maximum connect burst length: 0
> >> >> >
> >> >> > Total: connections 1 requests 1 replies 1 test-duration 0.011 s
> >> >> >
> >> >> > I also tried it with the same options as you used, and that seemed
> to
> >> >> work for me as well.
> >> >> >
> >> >> > Martin
> >> >> >
> >> >> >> -----Original Message-----
> >> >> >> From: httperf-bounces at napali.hpl.hp.com [mailto:httperf-
> >> >> >> bounces at napali.hpl.hp.com] On Behalf Of Delano Mandelbaum
> >> >> >> Sent: Thursday, November 27, 2008 6:23 AM
> >> >> >> To: httperf at napali.hpl.hp.com
> >> >> >> Subject: [httperf] Request Headers
> >> >> >>
> >> >> >> Hi,
> >> >> >>
> >> >> >> I'm using httperf 0.9.0 and I'd like to add HTTP headers to the
> >> >> >> requests. I've tried the following without success:
> >> >> >> httperf --hog --server=tp1 --uri=/small.html --num-conns=1 --
> rate=0
> >> >> >> --timeout=30 --think-timeout=0 −−add−header="X-Header: value\n"
> >> >> >> --print-request
> >> >> >>
> >> >> >> Is there something else I need to do to get this to work?
> >> >> >>
> >> >> >> Delano
> >> >> >>
> >> >> >> _______________________________________________
> >> >> >> httperf mailing list
> >> >> >> httperf at linux.hpl.hp.com
> >> >> >> http://www.hpl.hp.com/hosted/linux/mail-archives/httperf/
> >> >> >
> >> >
> >



More information about the httperf mailing list