upstream/mercurial-mirror Files · tests/test-unbundlehash.t

sslutil: try to find CA certficates in well-known locations...

sslutil: try to find CA certficates in well-known locations Many Linux distros and other Nixen have CA certificates in well-defined locations. Rather than potentially fail to load any CA certificates at all (which will always result in a certificate verification failure), we scan for paths to known CA certificate files and load one if seen. Because a proper Mercurial install will have the path to the CA certificate file defined at install time, we print a warning that the install isn't proper and provide a URL with instructions to correct things. We only perform path-based fallback on Pythons that don't know how to call into OpenSSL to load the default verify locations. This is because we trust that Python/OpenSSL is properly configured and knows better than Mercurial. So this new code effectively only runs on Python <2.7.9 (technically Pythons without the modern ssl module).

timeless - - Load All Authors

File last commit:

r28996:b74ca9ac stable


                r29500:4b16a5bd

default

Download file

             test-unbundlehash.t
        
                    45 lines
            
             | 1.4 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-unbundlehash.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      #require killdaemons

      Test wire protocol unbundle with hashed heads (capability: unbundlehash)

        $ cat << EOF >> $HGRCPATH

        > [experimental]

        > # This tests is intended for bundle1 only.

        > # bundle2 carries the head information inside the bundle itself and

        > # always uses 'force' as the heads value.

        > bundle2-exp = False

        > EOF

      Create a remote repository.

        $ hg init remote

        $ hg serve -R remote --config web.push_ssl=False --config web.allow_push=* -p $HGPORT -d --pid-file=hg1.pid -E error.log -A access.log

        $ cat hg1.pid >> $DAEMON_PIDS

      Clone the repository and push a change.

        $ hg clone http://localhost:$HGPORT/ local

        no changes found

        updating to branch default

        0 files updated, 0 files merged, 0 files removed, 0 files unresolved

        $ touch local/README

        $ hg ci -R local -A -m hoge

        adding README

        $ hg push -R local

        pushing to http://localhost:$HGPORT/

        searching for changes

        remote: adding changesets

        remote: adding manifests

        remote: adding file changes

        remote: added 1 changesets with 1 changes to 1 files

      Ensure hashed heads format is used.

      The hash here is always the same since the remote repository only has the null head.

        $ cat access.log | grep unbundle

        * - - [*] "POST /?cmd=unbundle HTTP/1.1" 200 - x-hgarg-1:heads=686173686564+6768033e216468247bd031a0a2d9876d79818f8f* (glob)

      Explicitly kill daemons to let the test exit on Windows

        $ killdaemons.py

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				#require killdaemons

				Test wire protocol unbundle with hashed heads (capability: unbundlehash)

				$ cat << EOF >> $HGRCPATH
				> [experimental]
				> # This tests is intended for bundle1 only.
				> # bundle2 carries the head information inside the bundle itself and
				> # always uses 'force' as the heads value.
				> bundle2-exp = False
				> EOF

				Create a remote repository.

				$ hg init remote
				$ hg serve -R remote --config web.push_ssl=False --config web.allow_push=* -p $HGPORT -d --pid-file=hg1.pid -E error.log -A access.log
				$ cat hg1.pid >> $DAEMON_PIDS

				Clone the repository and push a change.

				$ hg clone http://localhost:$HGPORT/ local
				no changes found
				updating to branch default
				0 files updated, 0 files merged, 0 files removed, 0 files unresolved
				$ touch local/README
				$ hg ci -R local -A -m hoge
				adding README
				$ hg push -R local
				pushing to http://localhost:$HGPORT/
				searching for changes
				remote: adding changesets
				remote: adding manifests
				remote: adding file changes
				remote: added 1 changesets with 1 changes to 1 files

				Ensure hashed heads format is used.
				The hash here is always the same since the remote repository only has the null head.

				$ cat access.log \| grep unbundle
				* - - [] "POST /?cmd=unbundle HTTP/1.1" 200 - x-hgarg-1:heads=686173686564+6768033e216468247bd031a0a2d9876d79818f8f (glob)

				Explicitly kill daemons to let the test exit on Windows

				$ killdaemons.py