Re: Capturing Cookies

2013-10-17 Thread Baptiste
Hi joseph,

Add the following to your frontend:
capture request header Cookie len64

Assuming you have alredy turned on option httplog.

Baptiste
 Le 16 oct. 2013 21:23, Joseph Hardeman jwharde...@gmail.com a écrit :

 Hey Guys,

 Quick questions, I want to capture what cookies are making it to an
 haproxy system, I know I can capture a cookie based off its name, but is
 there a way to capture all cookies when a browser hits my proxy?

 Thanks

 Joe



Reclutamiento, Entrevistas y Selección de Personal

2013-10-17 Thread Yair Vargas






  
  

  Reclutamiento, Entrevistas y Selección de 
  PersonalCali24deOctubre de 
2013
  

  Tomar una decisión equivocada al momento de 
  contratar un nuevo colaborador significa el desperdicio de una inversión 
  sustancial, no sólo en tiempo y dinero, sino de recursos de reclutamiento, 
  capacitación y beneficios. 
  
Para ampliar la información y obtener los 
  beneficios de inscripción temprana diligencie sin compromiso los 
  siguientes datos: -Nombre:-Empresa:-Ciudad:-Teléfono:-E-mail:haproxy@formilux.org"Su información jamás será 
  compartida ni comercializada. Garantizamos total confidencialidad y 
  privacidad de sus datos"Centro de atención telefónica: 01 8000 51 30 51, PBX (4) 444 
  09 18
  
Importante: En 
  cumplimiento con la ley 1581 de 2012, queremos comunicarle quesi 
  usted nodesea recibir la información actualizada con los temas más 
  innovadores de nuestra agenda de eventos de capacitación, puede des-suscribirse de estas invitaciones respondiendo 
  este correo con el asunto quit.La des-suscripción puede 
  tardar de 1 a 5 días.
  
Este correo 
  no puede ser considerado intrusivo ya que cumple con las políticas antispa 
  m internacionales y locales. Para des-suscribirse de estas invitaciones 
  responda este correo con el asunto remover.Este correo ha sido enviado 
  enviado a: 
haproxy@formilux.org



Unicode user-agent

2013-10-17 Thread Igor
Hi, I used hdr(user-agent) ACL to block some traffic, recently need to
block some Chinese named user-agent, does haproxy could handle this?

Thanks.

Bests,
-Igor



Re: Capturing Cookies

2013-10-17 Thread Joseph Hardeman
Hey Baptiste,

Very cool, thanks.  That is giving me what I needed.

Joe


On Thu, Oct 17, 2013 at 2:04 AM, Baptiste bed...@gmail.com wrote:

 Hi joseph,

 Add the following to your frontend:
 capture request header Cookie len64

 Assuming you have alredy turned on option httplog.

 Baptiste
  Le 16 oct. 2013 21:23, Joseph Hardeman jwharde...@gmail.com a écrit :

 Hey Guys,

 Quick questions, I want to capture what cookies are making it to an
 haproxy system, I know I can capture a cookie based off its name, but is
 there a way to capture all cookies when a browser hits my proxy?

 Thanks

 Joe




Capture IP Address

2013-10-17 Thread Phil Daws
Hello,

have searched but did not find an answer on whether its possible to pass the 
connecting IP address (src) as a variable on a redirect ?  This would be used 
on an ACL for certain access to URLs eg:

acl SEC_Admin url_dir -i /secure
acl ViaNOC src XXX.XXX.XXX.XX
redirect location http://internal.site?{SRC_IP} if SEC_Admin !ViaNOC

Is that possible ? Thank you.



Servicios informático

2013-10-17 Thread Prosistema
Prosistema un mail HTMLattachment: logo.jpg


RE: Unicode user-agent

2013-10-17 Thread Lukas Tribus
Hi Igor,


 Hi, I used hdr(user-agent) ACL to block some traffic, recently need to
 block some Chinese named user-agent, does haproxy could handle this?

The HTTP RFC only allows ASCII in the headers.


Lukas 


RE: SSL handshake failure

2013-10-17 Thread Lukas Tribus
Hi Thomas!

 We are using HAProxy v1.5-dev19, and are seeing a lot of the following
 errors in our haproxy logs:

 -- snip --
 Oct 16 02:24:22 localhost haproxy[2473]: some ip:44950
 [16/Oct/2013:02:24:22.643] https-in/1: SSL handshake failure
 Oct 16 02:30:47 localhost haproxy[2473]: some ip:37530
 [16/Oct/2013:02:30:47.436] https-in/1: SSL handshake failure
 Oct 16 02:32:09 localhost haproxy[2473]: some ip:32930
 [16/Oct/2013:02:32:08.709] https-in/1: SSL handshake failure
 Oct 16 02:32:28 localhost haproxy[2473]: some ip:38069
 [16/Oct/2013:02:32:27.731] https-in/1: SSL handshake failure
 -- snip --

 This error occurs at a rate of 0.7%. It most often happens via
 ColdFusion CFHTTP connections. Could there be any issues with HAProxy
 or is this a client connection issue?

Did you have an actual customer reporting issues or are you just seeing
this errors in the log?

Until you have a reported and confirmed issue, I wouldn't worry too much.
Clients may do bogus things, have transient network issues or simply die.
All those things may generate the error above.

Other software simply doesn't show you those errors.



Lukas 


Re: SSL handshake failure

2013-10-17 Thread Thomas Amsler
Lukas,

The folks that access our service via the ColdFusion CFHTTP method report
errors, because those calls fail, and thus they are not getting the
requested data.

-- Thomas


Best,
Thomas Amsler
http://gplus.to/tamsler


On Thu, Oct 17, 2013 at 10:41 AM, Lukas Tribus luky...@hotmail.com wrote:

 Hi Thomas!

  We are using HAProxy v1.5-dev19, and are seeing a lot of the following
  errors in our haproxy logs:
 
  -- snip --
  Oct 16 02:24:22 localhost haproxy[2473]: some ip:44950
  [16/Oct/2013:02:24:22.643] https-in/1: SSL handshake failure
  Oct 16 02:30:47 localhost haproxy[2473]: some ip:37530
  [16/Oct/2013:02:30:47.436] https-in/1: SSL handshake failure
  Oct 16 02:32:09 localhost haproxy[2473]: some ip:32930
  [16/Oct/2013:02:32:08.709] https-in/1: SSL handshake failure
  Oct 16 02:32:28 localhost haproxy[2473]: some ip:38069
  [16/Oct/2013:02:32:27.731] https-in/1: SSL handshake failure
  -- snip --
 
  This error occurs at a rate of 0.7%. It most often happens via
  ColdFusion CFHTTP connections. Could there be any issues with HAProxy
  or is this a client connection issue?

 Did you have an actual customer reporting issues or are you just seeing
 this errors in the log?

 Until you have a reported and confirmed issue, I wouldn't worry too much.
 Clients may do bogus things, have transient network issues or simply die.
 All those things may generate the error above.

 Other software simply doesn't show you those errors.



 Lukas


RE: SSL handshake failure

2013-10-17 Thread Lukas Tribus
Hi,


 Lukas,

 The folks that access our service via the ColdFusion CFHTTP method
 report errors, because those calls fail, and thus they are not getting
 the requested data.

It fails sporadically for some clients or it never works for specific
clients?

I would suggest:
- collect as much informations as possible about those clients (OS,
  platform, ssllib, browser, sw/hw firewall + other security products)
- try to find something affected clients all have in common and if possible:
- try reproducing it
- post the output of haproxy -vv, so we can see what openssl release you are
  running
- catch a failed request with tcpdump (-s0 to avoid truncating the packets;
  write it to a pcap file, not just stdout output)


This is most likely client related.


Regards,

Lukas 


возверните себе Возможность замечательно зреть

2013-10-17 Thread christinawilson
без операционный метод отвоевать зрение 
http://etnatour.com.ua/bitrix/backup/gmoom.htm



Tricky redirect... that needs help :)

2013-10-17 Thread Steven Le Roux
Hi,

What I want to do is :

acl p-static url_reg ^/context$
acl p-dynamic url_reg ^/context/.*$

reqrep ^([^\ ]*)\ /context/(.*) \1\ /\2 if p-dynamic

redirect code 301 location http://host.domain.tld/context if p-static
redirect code 301 prefix http://host.domain.tld/contex/ressource?id= if
p-dynamic


and then the dynamic redirection to be suffixed by the modified request.

As you noticed, redirect are processed before reqrep and I don't know how
to design this to have it working.

Thanks for your help

Regards,


-- 
Steven Le Roux
Jabber-ID : ste...@jabber.fr
0x39494CCB ste...@le-roux.info
2FF7 226B 552E 4709 03F0  6281 72D7 A010 3949 4CCB


Haproxy stats bug with nbproc 1

2013-10-17 Thread Boris

Hi,

With haproxy 1.4.22 and you enable the stats page (to 
monitor/enable/disable servers), it works great with nbproc set to 1(by 
default). When you enable nbproc  1, Each time you refresh the page, a 
different page is shown depending on the thread. This is really 
annoying. (and I would almost call it a bug) When you try to 
enable/disable servers through the web gui, you have to refresh multiple 
times (so it can cycle through every thread) to actually enable/disable 
a server. Will this be fixed in Haproxy 1.5? (or current in Git?) Thanks.



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




Cómo Optimizar el Control Interno para la Prevención de Fraudes

2013-10-17 Thread Yair Vargas






  
  

  Cómo 
  Optimizar el Control Interno para la Prevención de 
  FraudesCali13 - Bogotá14 
  -Medellín15 
  deNoviembre de 2013
  

  Las 
  operaciones diarias de los negocios son tan dinámicas, que se requiere de 
  un excelente control interno que garantice un confiable manejo de todas 
  las operaciones de la empresa. Los fraudes en compras, ventas, cobranzas, 
  inventarios y otras áreas vulnerables, son riesgos que se viven a diario, 
  situación por la cual debemos hacernos los siguientes cuestionamientos 
  ¿Nuestro sistema de control interno es efectivo? ¿Trabajamos para prevenir 
  o para detectar acciones fraudulentas? ¿Conocemos las áreas críticas de 
  nuestra organización que requieren controles 
estrictos?
  
Para ampliar la información y obtener los 
  beneficios de inscripción temprana diligencie sin compromiso los 
  siguientes datos: -Nombre:-Empresa:-Ciudad:-Teléfono:-E-mail: 
  haproxy@formilux.org"Su 
  información jamás será compartida ni comercializada. Garantizamos total 
  confidencialidad y privacidad de sus 
  datos"Centro de atención telefónica: 01 8000 51 30 51, PBX (4) 444 
  09 18
  
Importante: En 
  cumplimiento con la ley 1581 de 2012, queremos comunicarle quesi 
  usted nodesea recibir la información actualizada con los temas más 
  innovadores de nuestra agenda de eventos de capacitación, puede des-suscribirse de estas invitaciones respondiendo este 
  correo con el asunto quit.La des-suscripción puede tardar 
  de 1 a 5 días.
  
Este correo no puede ser 
  considerado intrusivo ya que cumple con las políticas antispa m 
  internacionales y locales. Para des-suscribirse de estas invitaciones 
  responda este correo con el asunto remover.Este correo ha sido enviado 
  enviado a: haproxy@formilux.org