view tests/test-hgweb-head.t @ 52289:323e3626929a

sslutil: add support for clients to set TLSv1.3 as the minimum protocol

AFAICT, all of the TLS versions are supported by the server without doing any
explicit work, and there's only a `devel` config to specify an exact version on
the server side.  Clients would also use TLSv1.3 if available, but this prevents
the server from negotiating down.  This also causes "tls1.3" to be listed in
`hg debuginstall`, even though it was previously supported (if the Python
intepreter supported it- IDK if there's a good way to proactively test for and
show future protocols without requiring manual updates like this).

The v1.3 tests are nested inside the v1.2 tests for simplicity.  The v1.2 blocks
already assume v1.0 and v1.1 support, so this seems reasonable for now.  If/when
the older protocols start getting dropped, this will have to be reworked anyway.

#require serve

Some tests for hgweb responding to HEAD requests

  $ hg init test
  $ cd test
  $ mkdir da
  $ echo foo > da/foo
  $ echo foo > foo
  $ hg ci -Ambase
  adding da/foo
  adding foo
  $ hg bookmark -r0 '@'
  $ hg bookmark -r0 'a b c'
  $ hg bookmark -r0 'd/e/f'
  $ hg serve -n test -p $HGPORT -d --pid-file=hg.pid -A access.log -E errors.log
  $ cat hg.pid >> $DAEMON_PIDS

manifest

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'file/tip/?style=raw' - date etag server
  200 Script output follows
  content-type: text/plain; charset=ascii
  
  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'file/tip/da?style=raw' - date etag server
  200 Script output follows
  content-type: text/plain; charset=ascii
  

plain file

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'file/tip/foo?style=raw' - date etag server
  200 Script output follows
  content-disposition: inline; filename="foo"
  content-length: 4
  content-type: application/binary
  

should give a 404 - static file that does not exist

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'static/bogus' - date etag server
  404 Not Found
  content-type: text/html; charset=ascii
  
  [1]

should give a 404 - bad revision

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'file/spam/foo?style=raw' - date etag server
  404 Not Found
  content-type: text/plain; charset=ascii
  
  [1]

should give a 400 - bad command

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'file/tip/foo?cmd=spam&style=raw' - date etag server
  400* (glob)
  content-type: text/plain; charset=ascii
  
  [1]

should give a 404 - file does not exist

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'file/tip/bork?style=raw' - date etag server
  404 Not Found
  content-type: text/plain; charset=ascii
  
  [1]

try bad style

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'file/tip/?style=foobar' - date etag server
  200 Script output follows
  content-type: text/html; charset=ascii
  

log

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'log?style=raw' - date etag server
  200 Script output follows
  content-type: text/plain; charset=ascii
  

access bookmarks

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'rev/@?style=paper' - date etag server
  200 Script output follows
  content-type: text/html; charset=ascii
  

static file

  $ get-with-headers.py localhost:$HGPORT --method=HEAD 'static/style-gitweb.css' - date etag server
  200 Script output follows
  content-length: 9074
  content-type: text/css
  

  $ killdaemons.py

  $ cd ..