hello!
thank you for the information, but it's still the same problem.
the backend proxies don't get up or down - no connection errors - so this can
not be the problem.
I call three different uris - (each a single picture) and each request goes to
the same backend proxy.
but when I test it with an other browser, then sometimes the backend proxy
changes.
I'm testing with three browsers from my PC:
firefox 3.6.8
IE 8
safari 5.0.1
is it possible, that the hash is not only generated of the uri, but also the user-agent or other
header information are used to build the hash too?
yours sincerely
<http://dict.leo.org/ende?lp=ende&p=Ci4HO3kMAA&search=Yours&trestr=0x8040>
Am 25.08.2010 19:25, schrieb Hervé COMMOWICK:
"hash-type" sorry, not "map-type"
Hervé.
On Wed, 25 Aug 2010 19:23:49 +0200
Hervé COMMOWICK<[email protected]> wrote:
Hello,
Can you see failed check in your stats page ? Because if one of your
server goes down, then came back, haproxy will probably send the
request to another server.
See "map-type" parameter in
http://haproxy.1wt.eu/download/1.4/doc/configuration.txt
"consistent" one will be good for you.
Hervé.
On Wed, 25 Aug 2010 18:00:01 +0200
Markus Fröhlich<[email protected]> wrote:
hi!
I'm using HA-Proxy version 1.4.8 2010/06/16 on SLES11 SP1 x64
my backend servers are three squid proxy servers to cache images.
what I want:
I'd like to cache each picture ONLY on one proxy server for
following reasons:
* it makes no sense to waste cache capacity and keep the same
picture in cache on all three proxy backends
* no different versions of the same picture, when the picture got
updated and the caching times of the proxies are different - so it
is possible, that one proxy shows the old picture and the others
the new one
so I use "balance uri" option
therefor a hash of the URI will be generated and haproxy will send
the same URI / hash always to the same backend proxy assumed the
backend server dosnt go down or squid isnt aviable. when I watch the
squid access logs of the backend proxies, it works sometimes and
sometimes I get the same picture (same URI) from an other proxy. why
isnt it persistant?!
the testet URIs look like this:
http://images5.<domain>.<TLD>/image_data/02/29/73/69.crop-100.80-80-80-80.orig.jpg?chk=340293d69ffc5d944a449891869f1a74
http://images5.<domain>.<TLD>/image_data/02/53/56/97.crop-100.120-120-120-120.orig.jpg?chk=7914ffc6a00d4702bdc3cdbd83bdbca9
http://images5.<domain>.<TLD>/image_data/dynimage/3b267cf984acb80a117454f0f6ae42df/1238e767062f89acba5faa86d994a789.gif?chk=793ecb49681273cbd9667578acbe4951
my haproxy.cfg:
global
node vvx-haproxy-03
user haproxy
group haproxy
daemon
maxconn 256
defaults
mode http
option clitcpka
timeout connect 5000ms
timeout client 50000ms
timeout server 50000ms
option httpchk
http-check send-state
frontend http-in
log /dev/log local0 debug
option httplog
option logasap
option socket-stats
bind x.x.x.x:80
acl invalid_src src 0.0.0.0/7 224.0.0.0/3
acl local_dst hdr(host) -i localhost
block if invalid_src || local_dst
default_backend proxy1
backend proxy1
log /dev/log local1 debug
option httplog
option tcplog
stats enable
stats hide-version
stats scope .
stats uri /xadmin?stats
stats realm HAproxy\ Statistics
stats auth xadmin:<pwd>
stats show-legends
fullconn 10000
balance uri len 128 depth 8
option srvtcpka
server p-01 10.x.x.x:80 maxconn 32 check inter 10000
server p-02 10.x.x.x:80 maxconn 32 check inter 10000
server p-03 10.x.x.x:80 maxconn 32 check inter 10000
--
Mit freundlichen Grüssen
Markus Fröhlich
Techniker
________________________________________________________
Xidras GmbH
Stockern 47
3744 Stockern
Austria
Tel: +43 (0) 2983 201 30503
Fax: +43 (0) 2983 201 305039
Email: [email protected]
Web: http://www.xidras.com
FN 317036 f | Landesgericht Krems | ATU64485024
________________________________________________________________________________
VERTRAULICHE INFORMATIONEN!
Diese eMail enthält vertrauliche Informationen und ist nur für den
berechtigten Empfänger bestimmt. Wenn diese eMail nicht für Sie bestimmt
ist, bitten wir Sie, diese eMail an uns zurückzusenden und anschließend
auf Ihrem Computer und Mail-Server zu löschen. Solche eMails und Anlagen
dürfen Sie weder nutzen, noch verarbeiten oder Dritten zugänglich
machen, gleich in welcher Form.
Wir danken für Ihre Kooperation!
CONFIDENTIAL!
This email contains confidential information and is intended for the
authorised recipient only. If you are not an authorised recipient,
please return the email to us and then delete it from your computer
and mail-server. You may neither use nor edit any such emails including
attachments, nor make them accessible to third parties in any manner
whatsoever.
Thank you for your cooperation
________________________________________________________________________________
