Hi,
Le 12/01/2015 22:27, RAKESH P B a écrit :
Hi All,
Can I have an update on this.
From what you describe and your configuration, this is not haproxy
related but you should take a look on the application or on the server
itself. But we can't tell you more, you didn't provide any information
on them.
By adding a X-Forwarded-Proto header, your server/application must take
it into account. And this is where there is no standard.
For example :
- some applications require X-Forwarded-Proto: https
- some others require that the server set an environment variables, and
depending on the component, it can have different names/values, some are
case sensitive, some others not (HTTPS=on, HTTPS=On, ...)
- apache redirects will use a special syntax on ServerName with a
https:// prefix, ...
As you see, it depends on what the developers thought at the time they
included SSL Offloading support.
On Sun, Jan 11, 2015 at 6:56 PM, RAKESH P B <[email protected]
<mailto:[email protected]>> wrote:
Please find updated configuration file.
On Sun, Jan 11, 2015 at 6:53 PM, RAKESH P B <[email protected]
<mailto:[email protected]>> wrote:
Hi Lukas,
Thanks you for the quick response. Please find the attached
Haproxy configuration.
On Sun, Jan 11, 2015 at 5:21 PM, Lukas Tribus
<[email protected] <mailto:[email protected]>> wrote:
> Hi Team,
>
> I have an issue Haproxy SSL redirection. Whenever any request is
> redirected from HAproxy , then two redirected request is send,
one is
> with http and other with https while URL for both request is same.
> For example,
> when the URL is redirected tohttps://www.example.com/to/path? ,
then
> these two request are send
>http://www.example.com/path1/path2/path3?
>https://www.example.com/path1/path2/path3?
Can you share the config?
Lukas
--
Cyril Bonté
