Paul Harrington wrote:

> So far so good. Seems to handle all of my cookie parsing stuff correctly.

That's a relief at least! ;-)

> I like the -w option. I would still like to see total_time include the
> time required to set up the ssl connection as this can have quite an impact -

This pre-6.5 does that. The start-time is now stored just after all the
options have been read. This should show the total execution time pretty
accurate. The end-time is set after the whole transfer is considered
complete.

As a side note, it turned out my selection of % wasn't that good for the
special-character (I deliberately did not select $ to avoid confusions in
perl/shell scripts). % happens to be a special character in DOS and
therefore all win32-users will need to write it '%%{variable}' instead...

Any other suggestions on how to write a variable? I do want the braces
there to clearly define the end of the variable name.

> might be nice to break the timings down to show the setup/transfer as
> seperate components.

They will appear as separate 'variables' for the -w option.

It also struck me that of course should -w also be able to read its string
from a file in the standard manner with -w @filename or -w @- for stdin.

> Also a variable containing the HTTP return code would be handy to save
> me having to grab the header.

That's a fair idea. The 'effective_url' variable is as another target
(suggested by Jörn Hartroth), which should show the actual (final) URL in
case there was one or more location follows.

--
   Daniel Stenberg - http://www.contactor.se/~dast - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol