1HTTPTEST(1)                       Cyrus IMAP                       HTTPTEST(1)
2
3
4

NAME

6       httptest - Cyrus IMAP documentation
7
8       Interactive HTTP test program.
9

SYNOPSIS

11       httptest [ -t keyfile ] [ -p port ] [ -m mechanism ] [ -a userid ]
12           [ -u userid ] [ -k num ] [ -l num ] [ -r realm ] [ -f file ]
13           [ -n num ] [ -s ] [ -c ] [ -i ] [ -v ] [ -w passwd ] [ -o option=value ] hostname
14

DESCRIPTION

16       This is actually installed as a hard linked copy of imtest(1).
17
18       httptest  is a utility that allows you to authenticate to a HTTP server
19       and interactively issue requests to  it.  Once  authenticated  you  may
20       issue any HTTP request by simply typing it in.  It is capable of multi‐
21       ple SASL authentication mechanisms and handles encryption layers trans‐
22       parently.  This  utility  is often used for testing the operation of an
23       http server. Also those developing HTTP clients find it useful.
24

OPTIONS

26       -t keyfile
27              Enable TLS.  keyfile contains the TLS public and  private  keys.
28              Specify  ""  to negotiate a TLS encryption layer but not use TLS
29              authentication.
30
31       -p port
32              Port to connect to. If left off this defaults to http as defined
33              in /etc/services.
34
35       -m mechanism
36              Force httptest to use mechanism for authentication. If not spec‐
37              ified, the strongest authentication mechanism supported  by  the
38              server  is chosen.  Specify one of Basic, Digest, NTLM, or Nego‐
39              tiate (GSS-SPNEGO).
40
41       -a userid
42              Userid to use for authentication; defaults to the current  user.
43              This  is  the  userid whose password or credentials will be pre‐
44              sented to the server for verification.
45
46       -u userid
47              Userid to use for authorization; defaults to the  current  user.
48              This  is the userid whose identity will be assumed after authen‐
49              tication.
50
51       -k num Minimum protection layer required.
52
53       -l num Maximum protection layer to use (0=none; 1=integrity; etc).  For
54              example  if  you are using the KERBEROS_V4 authentication mecha‐
55              nism specifying 0 will force imtest to not  use  any  layer  and
56              specifying  1  will  force  it  to  use the integrity layer.  By
57              default the maximum supported protection layer will be used.
58
59       -r realm
60              Specify the realm  to  use.  Certain  authentication  mechanisms
61              (e.g. DIGEST-MD5) may require one to specify the realm.
62
63       -f file
64              Pipe file into connection after authentication.
65
66       -n num Number of authentication attempts; default = 1.  The client will
67              attempt to do SSL/TLS session reuse  and/or  fast  reauth  (e.g.
68              DIGEST-MD5), if possible.
69
70       -s     Enable HTTP over SSL (https).
71
72       -c     Enable  challenge  prompt  callbacks.   This  will cause the OTP
73              mechanism to ask for the the one-time password  instead  of  the
74              secret pass-phrase (library generates the correct response).
75
76       -i     Don't  send an initial client response for SASL mechanisms, even
77              if the protocol supports it.
78
79       -v     Verbose. Print out more information than usual.
80
81       -w     Password to use (if not supplied, we will prompt).
82
83       -o option=value
84              Set the SASL option to value.
85

EXAMPLES

SEE ALSO
88       httpd(8)
89

AUTHOR
91       The Cyrus Team
92

94       1993-2017, The Cyrus Team
95
96
97
98
993.0.13                         December 16, 2019                   HTTPTEST(1)



        

    


            
        

        

            Impressum