Kallithea issues archive

Issue #34: Possible regression: displaying changeset fails on 0.1

Reported by: Bernhard Weitzhofer
State: resolved
Created on: 2014-09-09 16:42
Updated on: 2014-09-29 12:48


We have Installed Kallithea 0.1 pretty much like it's recommended in the docs.

Unfortunately, trying to view a changeset, we get an HTTP 500. The relevant portion of the logfile is included.

The exact same configuration works for Kallithea 0.0 (pip install kallithea==0.1 being the only difference).




Comment by Mads Kiilerich, on 2014-09-09 19:21

This is issue #24 and fixed in https://kallithea-scm.org/repos/kallithea/changeset/bbf4118f6e0f21c62439f2e108c225d24dc05d9e

You can test it by running from a checkout as described on https://bitbucket.org/conservancy/kallithea/wiki/Home .

I don't use git and do not know exactly what caused the problem. You can perhaps bisect and find out what caused it so we can be sure it really has been fixed.

Comment by al zi, on 2014-09-29 08:03

Yeap, this bug is comfirmed.

Caused by switching internal request from https:// scheme to http://

Looks like it ignores force_https setting in production.ini

Comment by Mads Kiilerich, on 2014-09-29 10:20

al: this bug had nothing todo with https.

Comment by al zi, on 2014-09-29 11:06

Anyway, after upgrading 0.0->0.1 It shows me in trace that requested url change scheme from https to http This is really annoying and causing many problems like "logout" and other redirects as my 80 port is disabled on apache

Comment by Mads Kiilerich, on 2014-09-29 12:48

That sounds like a configuration issue. Try to ask the community on the mailing list. If you can narrow it down to a bug report but can't fix it, please file a separate issue.