Subject: [Pound Mailing List] HeadRequire check http and https? - msg#00067

Previous Message by Date: click to view message preview

[Pound Mailing List] Dynamic rescaling calculations

Currently, when dynamic rescaling is being done all requests (and their response times) are treated equally. Meaning, if you have a responses of HTTP 200 or a 500 error, they are both treated equally, and response times from both are used for dynamic rescaling later. In my opinion, this should be amended to include only responses with good return codes (200 only). At the very least, I believe, 500 level messages should be excluded. Basically, if the backend's application has crashed, the backend http server response time should not be used for dynamic rescaling (the response time could be too slow or too fast, not indicative of the server's response speed). What do you think? -- To unsubscribe send an email with subject 'unsubscribe' to pound-Ws3YcLWMCpvhvxM+mQhndA@xxxxxxxxxxxxxxxx Please contact roseg-Ws3YcLWMCps@xxxxxxxxxxxxxxxx for questions. http://www.apsis.ch/pound/pound_list/archive/2007/2007-03/1174081075000

Next Message by Date: click to view message preview

Re: [Pound Mailing List] HeadRequire check http and https?

michael.ringler-DbE67O1B+V0b1SvskN2V4Q@xxxxxxxxxxxxxxxx wrote: Hello, I would like to check the incoming URL if http or https. I tried the HeadRequire-Option in the Service-Section but it seems that only the domain without http|https is checked. The URL-Options checks only the text after the domain so it does not work too. How can I do this? Perhaps with an another option and not with HeadRequire? Example: (with my own syntax, which does not work but I wish it would) ... Service HeadRequire "^http://.*" Backend Address 1.2.3.4 Port 80 End End Service HeadRequire "^https://.*" Backend Address 5.6.7.8 Port 80 End End ... Thanks Michael Ringler You should be able to distinguish between http and https in you ListentHTTP and ListenHTTPS directives. You can put a service in each one to separate requests for http/https traffic to go to different backends. You can also put a directive like with AddHeader into either ListenHTTP or ListenHTTPS so you can distinguish the http vs https on your backend (for example, you can put 'AddHeader "Front-End-Https: on" ' in your ListenHTTPS and then check for Fron-End-Https header on your backends) -- To unsubscribe send an email with subject 'unsubscribe' to pound-Ws3YcLWMCpvhvxM+mQhndA@xxxxxxxxxxxxxxxx Please contact roseg-Ws3YcLWMCps@xxxxxxxxxxxxxxxx for questions. http://www.apsis.ch/pound/pound_list/archive/2007/2007-03/1174318888000/1174319991000

Previous Message by Thread: click to view message preview

[Pound Mailing List] Dynamic rescaling calculations

Currently, when dynamic rescaling is being done all requests (and their response times) are treated equally. Meaning, if you have a responses of HTTP 200 or a 500 error, they are both treated equally, and response times from both are used for dynamic rescaling later. In my opinion, this should be amended to include only responses with good return codes (200 only). At the very least, I believe, 500 level messages should be excluded. Basically, if the backend's application has crashed, the backend http server response time should not be used for dynamic rescaling (the response time could be too slow or too fast, not indicative of the server's response speed). What do you think? -- To unsubscribe send an email with subject 'unsubscribe' to pound-Ws3YcLWMCpvhvxM+mQhndA@xxxxxxxxxxxxxxxx Please contact roseg-Ws3YcLWMCps@xxxxxxxxxxxxxxxx for questions. http://www.apsis.ch/pound/pound_list/archive/2007/2007-03/1174081075000

Next Message by Thread: click to view message preview

Re: [Pound Mailing List] HeadRequire check http and https?

michael.ringler-DbE67O1B+V0b1SvskN2V4Q@xxxxxxxxxxxxxxxx wrote: Hello, I would like to check the incoming URL if http or https. I tried the HeadRequire-Option in the Service-Section but it seems that only the domain without http|https is checked. The URL-Options checks only the text after the domain so it does not work too. How can I do this? Perhaps with an another option and not with HeadRequire? Example: (with my own syntax, which does not work but I wish it would) ... Service HeadRequire "^http://.*" Backend Address 1.2.3.4 Port 80 End End Service HeadRequire "^https://.*" Backend Address 5.6.7.8 Port 80 End End ... Thanks Michael Ringler You should be able to distinguish between http and https in you ListentHTTP and ListenHTTPS directives. You can put a service in each one to separate requests for http/https traffic to go to different backends. You can also put a directive like with AddHeader into either ListenHTTP or ListenHTTPS so you can distinguish the http vs https on your backend (for example, you can put 'AddHeader "Front-End-Https: on" ' in your ListenHTTPS and then check for Fron-End-Https header on your backends) -- To unsubscribe send an email with subject 'unsubscribe' to pound-Ws3YcLWMCpvhvxM+mQhndA@xxxxxxxxxxxxxxxx Please contact roseg-Ws3YcLWMCps@xxxxxxxxxxxxxxxx for questions. http://www.apsis.ch/pound/pound_list/archive/2007/2007-03/1174318888000/1174319991000