Hi  Jeff,joris

Actually this is what i am looking for exactly for our production the
earlier configuration for a test server only
but the below is the exact thing which i am looking for can you please help
on this please its very urgent for me

Currently the connector is pointing to 192.168.104.109.
When the connector (windows service OpsPRD) is started on fdev2 server it
will first make a http URL call to the server 192.168.104.109 with the URL:
/ispring/FileReaderServlet?fileName=lib/properties/ispring_properties.xml&prj=274006AB_1837_48D1_A597_48A29B86A52D

Here prj=274006AB_1837_48D1_A597_48A29B86A52D is the parameter which will
help us decide where we want to route the tcp traffic.
Lets say, if the parameter prj is equal to
274006AB_1837_48D1_A597_48A29B86A52D then it should get routed to
prdappc2n2.
For anything else it should go to prdappc2n1.




Regards
Nitesh

On Sat, Sep 19, 2015 at 7:45 PM, Jeff Palmer <[email protected]> wrote:

> I also noticed, you aren't doing anything on the frontend to determine if
> the connection is TCP or http.  In fact, this looks nothing like the
> example configuration I suggested.
> On Sep 19, 2015 10:12 AM, "Jeff Palmer" <[email protected]> wrote:
>
>> As I previously mentioned, your frontend will need to use mode TCP.  You
>> v have a defaults of mode http, and don't  change the mode on your front
>> end.
>>
>> Give that a try, and report back.
>> On Sep 19, 2015 9:44 AM, "Nitesh Kumar Gupta" <[email protected]>
>> wrote:
>>
>>>
>>> Hi All,
>>>
>>> I am repeating my question again coz all the suggestions din't here
>>>
>>> I am having 4 servers
>>>
>>> server1
>>> server2
>>> server3
>>> server4
>>>
>>>
>>> Now what i want
>>>
>>> if any request come from dev1.server.com that should forward to tcp on
>>> server4 and the normal opertion should be between the rest there servers
>>>
>>> I am using below configuration file but that is not working
>>>
>>> Please check the below config and provide me proper solution
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> global
>>>     log         127.0.0.1 local0
>>>     log         127.0.0.1 local1 debug
>>>     chroot      /var/lib/haproxy
>>>     pidfile     /var/run/haproxy.pid
>>>     maxconn     4000
>>>     user        haproxy
>>>     group       haproxy
>>>     daemon
>>>     stats socket /var/lib/haproxy/stats
>>>
>>> defaults
>>>     mode                    http
>>>     log                     global
>>>     option                  tcplog
>>>     option                  dontlognull
>>>     option http-server-close
>>>     option                  redispatch
>>>     retries                 3
>>>     timeout http-request    10s
>>>     timeout queue           1m
>>>     timeout connect         10s
>>>     timeout client          1m
>>>     timeout server          1m
>>>     timeout http-keep-alive 10s
>>>     timeout check           10s
>>>     maxconn                 3000
>>>
>>> frontend haproxy_in
>>>         bind *:80
>>>         default_backend haproxy_http
>>>     option httplog
>>>     acl host1 hdr(host) -i dev1.server.com
>>>
>>>     use_backend haproxy_http_tcp if host1
>>> backend haproxy_http
>>>         balance roundrobin
>>>         mode http
>>>         server server1 server1:80         weight 1 maxconn 512 check
>>>     server server2 server2:80         weight 1 maxconn 512 check
>>>     server server3 server3:80         weight 1 maxconn 512 check
>>>
>>> backend haproxy_http_tcp
>>>     bind *:443
>>>     mode tcp
>>>         option tcplog
>>>     server server4 server4:80         weight 1 maxconn 512 check
>>>
>>>
>>> #listen https
>>> #    bind *:443
>>> #    mode tcp
>>> #    option tcplog
>>> #    balance roundrobin
>>> #       server vm1 prdappc2n2:443      weight 1 maxconn 512 check
>>>
>>>
>>> On Fri, Sep 18, 2015 at 12:24 PM, joris dedieu <[email protected]>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> 2015-09-18 3:13 GMT+02:00 Nitesh Kumar Gupta <[email protected]
>>>> >:
>>>> > Hi,
>>>> >
>>>> > I want to setup haproxy in way there that will work on both http and
>>>> https
>>>> > and also tpc but that will be conditional mean if any perticular link
>>>> will
>>>> > come that will go via tcp
>>>> >
>>>> > So can you help me how can i setup this
>>>>
>>>> You may find a lot of useful ressources by searching how make ssh and
>>>> https work on the same port with haproxy. This is a common case on
>>>> using http and tcp stuff on the same port (to bypass corporate proxies
>>>> I presume).
>>>>
>>>> Joris
>>>>
>>>>
>>>> >
>>>> > --
>>>> > Regards
>>>> > Nitesh Kumar Gupta
>>>>
>>>
>>>
>>>
>>> --
>>> Regards
>>> Nitesh Kumar Gupta
>>>
>>


-- 
Regards
Nitesh Kumar Gupta

Reply via email to