HTTPS redirects back to HTTP

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Host Gitblit behind https
2. Log in to Gitblit

What is the expected output? What do you see instead?

Expect for it to log in and view repositories. It logs in OK, but it gives an 
error:

====
Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
====

Showing that we are being redirected to http.

I need to press the browser's back button for it to work OK.

Original issue reported on code.google.com by arthurbu...@gmail.com on 10 Jul 2014 at 8:37

[GoogleCodeExporter]

You are running Gitblit behind an https proxy, right?  I've seen this too.  
Will investigate after I return from vacation.

Original comment by James.Mo...@gmail.com on 10 Jul 2014 at 12:27

• Changed state: Accepted
• Added labels: Milestone-1.6.1

[GoogleCodeExporter]

Yes I am running it behind an https proxy

Original comment by arthurbu...@gmail.com on 10 Jul 2014 at 12:50

[GoogleCodeExporter]

Hi,

I experience a similar issue, which might share the same root cause. Our 
Git:Blit service is https only, and some users reported issues with the web 
interface.

The affected users access the service through a Firewall which blocks port 80. 
Although Git:Blit and Apache are configured with SSL support as described in 
the docs, Git:Blit redirects the user to http://hostname/ after Log-in and 
Log-out. So every log-in attempt for the affected users ends in a time-out.

@James: Were you already able to look into this?

Br,
Tom.

Original comment by d...@sigsegv.at on 17 Sep 2014 at 9:25

[GoogleCodeExporter]

There are two issues blocking 1.6.1 release.  This is one of them.

Original comment by James.Mo...@gmail.com on 17 Sep 2014 at 7:15

[GoogleCodeExporter]

v1.6.1 released

Original comment by James.Mo...@gmail.com on 20 Oct 2014 at 9:36

• Changed state: Done