GFI Forums: Kerio Connect » Kerio Connect redirects from HTTPS to HTTP

Home » GFI User Forums » Kerio Connect » Kerio Connect redirects from HTTPS to HTTP

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Kerio Connect redirects from HTTPS to HTTP [message #129200 is a reply to message #129192]

Tue, 26 April 2016 11:33

Pavel Dobry (Kerio) is currently offline

Pavel Dobry (Kerio)
Messages: 2057
Registered: October 2003
Location: Czech Republic

JeroenW wrote on Mon, 25 April 2016 19:18

There are no HTTP headers modified or added by WinGate. Kerio Connect should not redirect to HTTPS, this option is not enabled. Kerio Connect redirects to HTTP instead of HTTPS and that is the problem, it should not redirect at all. I have not configured Kerio Connect to only accept certain host headers, I don't even know how to do that. Users reach Kerio Connect through the proxy using a hostname that internally resolves to the local IP address of the Kerio Connect server.

I can modify or add headers to be sent to the Kerio Connect server if required.

Kerio Connect gets a connection from HTTP (from WinGate) so it redirects it to HTTP. Redirections in HTTP are normal - that is the only way how you can move browser to another URL.

The problem is that Wingate is hiding original protocol and it does not rewrite Location: header in HTTP responses.

Knowledge Base: http://manuals.gfi.com/en/kerio/home/Content/Home.htm.

Report message to a moderator

Re: Kerio Connect redirects from HTTPS to HTTP [message #129209 is a reply to message #129200]

Tue, 26 April 2016 16:10

JeroenW
Messages: 14
Registered: March 2016

Other web sites that we host behind WinGate never redirect using full http URLs, only relative paths. Therefore this problem does not occur. If Kerio Connect does use full URLs I think this should be changed.

Of course replacing "http://" for "https://" in the location headers that Kerio Connect sends to the client will circumvent the problem. But prevention is better than cure. Plus I can't seem to do this using this version of WinGate.

I think the question that remains is: can these full URL redirections be changed to relative paths? Or can I change this myself somehow?

Report message to a moderator

Re: Kerio Connect redirects from HTTPS to HTTP [message #129210 is a reply to message #129209]

Tue, 26 April 2016 16:37

Pavel Dobry (Kerio)
Messages: 2057
Registered: October 2003
Location: Czech Republic

Now I understand it. It is not about HTTPS redirection (which is a consequence) but about absolute URI in HTTP redirect.
We will check if this can be changed.

Knowledge Base: http://manuals.gfi.com/en/kerio/home/Content/Home.htm.

Report message to a moderator

Re: Kerio Connect redirects from HTTPS to HTTP [message #129212 is a reply to message #129210]

Tue, 26 April 2016 17:47

JeroenW
Messages: 14
Registered: March 2016

When you know for sure, can you inform me íf you are going to make this change and if so, when?
Thanks in advance!

Report message to a moderator

Re: Kerio Connect redirects from HTTPS to HTTP [message #129225 is a reply to message #129212]

Wed, 27 April 2016 18:33

Pavel Dobry (Kerio)
Messages: 2057
Registered: October 2003
Location: Czech Republic

Absolute URI was required by RFC 2616 until 2014. Kerio Connect is compliant with this RFC due to compatibility with browsers.
Updated RFC 7231 now allows also relative URI in redirect response. Because the list of browsers supported in Kerio Connect client is focused on modern browsers, we will evaluate an option to use relative URI.

BTW: WinGate seems to be only reverse proxy server which cannot handle properly HTTP/1.1 protocol as defined in RFC 2616. Consider that.

Knowledge Base: http://manuals.gfi.com/en/kerio/home/Content/Home.htm.

Report message to a moderator

Pages (2): [ « ‹ 1 2]

Previous Topic:	Outlook 2016 on Windows with KC 9.0.2
Next Topic:	"Inbox 1" in Outlook 2010 KOFF

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Sep 27 18:44:32 CEST 2023

Total time taken to generate the page: 0.07305 seconds