Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-14 Thread Susheel Jalali
Communications Solutions' posted at: www(DOT)Coscend(DOT)com/Terms_and_Conditions.html -- Original Message Subject: Re: HTTP Response Rewriting to Replace Internal IP with FQDN From: Aleksandar Lazic <al-h

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-14 Thread Aleksandar Lazic
Subject: Re: HTTP Response Rewriting to Replace Internal IP with FQDN From: Aleksandar Lazic <al-hapr...@none.at> Date: Tue, October 13, 2015 2:44 pm To: Susheel Jalali <susheel.jal...@coscend.com> Cc: haproxy@formilux.org, "i...@coscend.com" <i...@coscend.com>

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-13 Thread Susheel Jalali
Dear Aleks, Thank you for your continued help. As you advised, we did the following. We would appreciate any guidance you could give to solve this issue. (1) We ran haproxy (1.5.14) in debug mode in two use cases for Product1. The debug output for each case is posted below. (2) Also, as

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-13 Thread Aleksandar Lazic
Dear Susheel Jalali. Am 13-10-2015 22:20, schrieb Susheel Jalali: Dear Aleks, [snipp] ++ Tomcat’s web.xml In web.xml, the context parameter is: globalScope default and the filter mapping for the application is: Product1Application

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-13 Thread Aleksandar Lazic
Am 13-10-2015 23:36, schrieb Aleksandar Lazic: Dear Susheel Jalali. Am 13-10-2015 22:20, schrieb Susheel Jalali: Dear Aleks, [snipp] ++ Tomcat’s web.xml In web.xml, the context parameter is: globalScope default and the filter mapping for the

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-12 Thread Susheel Jalali
Dear HAProxy Developer community, We are seeking your inputs in the following issue we are facing: We would like to access Product1 via URL: https://coscend.com:14443/Product1/ , wherein 14443 is port forwarded by router to 443 inside the server. Output URL from the Product1 server should

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-12 Thread Aleksandar Lazic
Dear Susheel Jalali. Am 12-10-2015 22:06, schrieb Susheel Jalali: Dear HAProxy Developer community, We are seeking your inputs in the following issue we are facing: We would like to access Product1 via URL: https://coscend.com:14443/Product1/ , wherein 14443 is port forwarded by router to

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-07 Thread Aleksandar Lazic
Dear Susheel Jalali. Am 07-10-2015 23:24, schrieb Susheel Jalali: Dear Igor and Aleks, Thank you for your insights. Very useful to us, as we are implementing HAProxy for the first time. Below we have described how we have implemented your advise and the result. Output of "haproxy -vv" is

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-07 Thread Susheel Jalali
Dear Igor and Aleks, Thank you for your insights. Very useful to us, as we are implementing HAProxy for the first time. Below we have described how we have implemented your advise and the result. Output of "haproxy -vv" is given at end. We have also provided the configuration file and

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-07 Thread Aleksandar Lazic
Hi Susheel Jalali. please can you show us the out put of haproxy -vv Am 06-10-2015 22:06, schrieb Susheel Jalali: Dear HAProxy Developers, After incorporating insights from Bryan Talbot and articles from Baptiste Assman on HAProxy Web site, we have been able to get the basic configuration of

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

2015-10-06 Thread Igor Cicimov
On Wed, Oct 7, 2015 at 7:06 AM, Susheel Jalali wrote: > Dear HAProxy Developers, > > After incorporating insights from Bryan Talbot and articles from Baptiste > Assman on HAProxy Web site, we have been able to get the basic > configuration of HAProxy going. Now we