##// END OF EJS Templates
upstream » kallithea
RSS

Clone from https://kallithea-scm.org/repos/kallithea

auth: only use X- headers instead of wsgi.url_scheme if explicitly told so in url_scheme_header - drop https_fixup setting...
auth: only use X- headers instead of wsgi.url_scheme if explicitly told so in url_scheme_header - drop https_fixup setting Before, several X- headers would be trusted to overrule the actual connection protocol (http or https) seen by the Kallithea WSGI server. That was mainly when https_fixup were set, but it incorrectly also kicked in if https_fixup or use_htsts were configured. The ambiguity of which headers were used also made it less reliable. The proxy server not only had to be configured to set one of the headers correctly, it also had to make sure other headers were not passed on from the client. It would thus in some cases be possible for clients to fake the connection scheme, and thus potentially be possible to bypass restrictions configured in Kallithea. Fixed by making it configurable which WSGI environment variable to use for the protocol. Users can configure url_scheme_header to for example HTTP_X_FORWARDED_PROTO instead of using the default wsgi.url_scheme . This change is a bit similar to what is going on in the https_fixup middleware, but is doing a bit more of what for example is happening in similar code in werkzeug/middleware/proxy_fix.py . The semantics of the old https_fixup were unsafe, so it has been dropped. Admins that are upgrading must change their configuration to use the new url_scheme_header option.
Thomas De Schampheleire - - Load All Authors

File last commit:

r7261:52f823b9 default
r8680:070b8c39 default
Show More
vcs_setup.rst
61 lines | 1.7 KiB | text/x-rst | RstLexer
/ docs / administrator_guide / vcs_setup.rst
History | Annotation | Raw |Copy content |Copy permalink

Version control systems setup

Kallithea supports Git and Mercurial repositories out-of-the-box. For Git, you do need the git command line client installed on the server.

You can always disable Git or Mercurial support by editing the file kallithea/__init__.py and commenting out the backend. For example, to disable Git but keep Mercurial enabled:

BACKENDS = {
    'hg': 'Mercurial repository',
    #'git': 'Git repository',
}

Git-specific setup

Web server with chunked encoding

Large Git pushes require an HTTP server with support for chunked encoding for POST. The Python web servers waitress and gunicorn (Linux only) can be used. By default, Kallithea uses waitress for gearbox serve instead of the built-in paste WSGI server.

The web server used by gearbox is controlled in the .ini file:

use = egg:waitress#main

or:

use = egg:gunicorn#main

Also make sure to comment out the following options:

threadpool_workers =
threadpool_max_requests =
use_threadpool =

Increasing Git HTTP POST buffer size

If Git pushes fail with HTTP error code 411 (Length Required), you may need to increase the Git HTTP POST buffer. Run the following command as the user that runs Kallithea to set a global Git variable to this effect:

git config --global http.postBuffer 524288000