Nous vous créons un nouveau site internet clé en main
Bonjour, Depuis que Google a commencé à pénaliser les sites internet non Responsive au mois de mars dernier, nous vous proposons la refonte ou la création de votre site internet référencement compris. Implantés dans le 11ème arrondissement de Paris, nous intervenons auprès des TPE / PME pour apporter une réponse personnalisée à leurs besoins en communication sur Internet : Sites vitrine, e-commerce, référencement naturel. La technologie phare en matière de site internet agréé par Google s'appelle Responsive design. Grace à cette nouvelle technologie notre site est en première page Google avec les mots clés comme : " Création de site internet 75000 " première page sur Google : www.altech-france.fr " Renforcement structure Paris" première page sur Google : www.renforcement-structure.fr Pour ne citer que ceux-là ! POUR UN DEVIS GRATUIT CLIQUER-ICI En vous remerciant pour votre attention, nous restons à votre disposition pour tous renseignements complémentaires. Cordialement. Service client Pour plus d'informations : Cliquez-ici Ne plus recevoir de message :http://boomjets.fr/unsubscribe.php?M=1149748=0ef16245c3d1a39c201947e309604292=15=38
Re: lua, changing response-body in http pages 'supported' ?
Hi Thierry, haproxy-list, Op 19-10-2015 om 11:24 schreef thierry.fourn...@arpalert.org: On Mon, 19 Oct 2015 01:31:42 +0200 PiBa-NLwrote: Hi Thierry, Op 18-10-2015 om 21:37 schreef thierry.fourn...@arpalert.org: On Sun, 18 Oct 2015 00:07:13 +0200 PiBa-NL wrote: Hi haproxy list, For testing purposes i am trying to 'modify' a response of a webserver but only having limited success. Is this supposed to work? As a more usefull goal than the current LAL to TST replacement i imagine rewriting absolute links on a webpage could be possible which is sometimes problematic with 'dumb' webapplications.. Or is it outside of the current scope of implemented functionality? If so, it on the 'lua todo list' ? I tried for example a configuration like below. And get several different results in the browser. -Sometimes i get 4 times TSTA -Sometimes i see after the 8th TSTA- Connection: keep-alive << this happens most of the time.. -Sometimes i get 9 times TSTA + STOP << this would be the desired outcome (only seen very few times..) Probably due to the response-buffer being filled differently due to 'timing'.. The "connection: keep-alive" text is probably from the actual server reply which is 'appended' behind the response generated by my lua script.?. However shouldn't the .done() prevent that from being send to the client? Ive tried putting a loop into the lua script to call res:get() multiple times but that didnt seem to work.. Also to properly modify a page i would need to know all changes before sending the headers with changed content-length back to the client.. Can someone confirm this is or isn't (reliably) possible? Or how this can be scripted in lua differently? Hello, Your script replace 3 bytes by 3 bytes, this must run with HTTP, but if your replacement change the length of the response, you can have some difficulties with clients, or with keepalive. Yes i started with replacing with the same number of bytes to avoid some of the possible troubles caused by changing the length.. And as seen in the haproxy.cfg it is configured with 'mode http'. The res:get(), returns the current content of the response buffer. Maybe it not contains the full response. You must execute a loop with regular "core.yield()" to get back the hand to HAProxy and wait for new Calling yield does allow to 'wait' for more data to come in.. No guarantee that it only takes 1 yield for data to 'grow'.. [info] 278/055943 (77431) : luahttpresponse Content-Length XYZ: 14115 [info] 278/055943 (77431) : luahttpresponse SIZE: 2477 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 6221 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 7469 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 7469 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 7469 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 7469 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 7469 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 7469 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 7469 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 8717 [info] 278/055943 (77431) : luahttpresponse LOOP [info] 278/055943 (77431) : luahttpresponse SIZE: 14337 [info] 278/055943 (77431) : luahttpresponse DONE?: 14337 data. When all the data are read, res:get() returns an error. Not sure when/how this error would happen.? The result of res:get only seems to get bigger while the webserver is sending the response.. The res:send() is dangerous because it send data directly to the client without the end of haproxy analysis. Maybe it is the cause o your problem. Try to use res:set(). Ok tried that, new try with function below. The difficulty is that another "res:get()" returns the same data that these you put. I don't known if you can modify an http response greater than one buffer. Would be nice if that was somehow possible. But my current lua script cannot.. The function res:close() closes the connection even if HAProxy want to keep the connection alive. I suggest that you don't use this function. It seems txn.res:close() does not exist? txn:done() I reproduce the error message using curl. By default curl tries to transfer data with keepalive, and it is not happy if the all the announced data are not transfered. Connection: keep-alive curl: (18) transfer closed with outstanding read data remaining It seems that i reproduce a bug. I'm looking for. Ok if you can create a patch, let me know. Happy to test if it solves some of the issues i see. Hi, I catch the error. While
Re: httpchk failures
Benjamin Smithwrites: > > Igor, > > Thanks for the response; I didn't see this email until just now as it didn't > go through the mailing list and so wasn't filtered as expected. > > I spent my morning trying everything I could think of to get haproxy's agent- > check to work consistently. The main symptom is that haproxy would mark hosts > with the status of "DRAIN" and provide no clues as to why, even with log- > health-checks on. After a *lot* of trial and error, I've found the following > that seem to be bugs, on the latest 1.5.11 release, running on CentOS 6. > > 1) agent-check output words sometimes handled inconsistently, ignored, or > misunderstood if " " was used instead of "," as a separator. > > This is understood: > echo "ready,78%\r\n" > > This line often causes a DRAIN state. A restart of haproxy was insufficient to > clear the DRAIN state: (see #3) > echo "ready 78%\r\n" > > 2) Inconsistent logging of DRAIN status change when health logging was on. > (the server would turn blue in the stats page without any logging as to why. > Logging status would sometimes say " Server $service/$name is UP (leaving > forced drain)" even as the stats page continues to report DRAIN state! > > 3) Even when the agent output was amended as above, for hosts that were set to > the DRAIN state pursuant to #1 issue were not brought back to ready/up state > until "enable health $service/$host" and/or "enable agent $service/$host" was > sent to the stats port. > > 4) Setting the server weight to 10 seems to help a significant amount. If, in > fact, haproxy can't handle 35% of 1 it should throw an error on startup IMHO. > > See also my comments interspersed below: > > Thanks, > > Benjamin Smith > > On Tuesday, April 14, 2015 10:50:31 AM you wrote: > > On Tue, Apr 14, 2015 at 10:11 AM, Igor Cicimov < > > > > igorc@...> wrote: > > > On Tue, Apr 14, 2015 at 5:00 AM, Benjamin Smith > > > > > > wrote: > > >> We have 5 Apache servers behind haproxy and we're trying to enable use > > >> the > > >> "httpchk" option along with some performance monitoring. For some reason, > > >> haproxy keeps thinking that 3/5 apache servers are "down" even though > > >> it's > > >> obvious that haproxy is both asking the questions and the servers are > > >> answering. > > >> > > >> Is there a way to log httpchk failures? How can I ask haproxy why it > > >> seems to > > >> think that several apache servers are down? > > >> > > >> Our config: > > >> CentOS 6.x recently updated, 64 bit. > > >> > > >> Performing an agent-check manually seems to give good results. The below > > >> result is immediate: > > >> [root xr1 ~]# telnet 10.1.1.12 9333 > > >> Trying 10.1.1.12... > > >> Connected to 10.1.1.12. > > >> Escape character is '^]'. > > >> up 78% > > >> Connection closed by foreign host. > > >> > > >> > > >> I can see that xinetd on the logic server got the response: > > >> Apr 13 18:45:02 curie xinetd[21890]: EXIT: calcload333 status=0 pid=25693 > > >> duration=0(sec) > > >> Apr 13 18:45:06 curie xinetd[21890]: START: calcload333 pid=26590 > > >> from=:::10.1.1.1 > > >> > > >> > > >> I can see that apache is serving happy replies to the load balancer: > > >> [root curie ~]# tail -f /var/log/httpd/access_log | grep -i "10.1.1.1 " > > >> 10.1.1.1 - - [13/Apr/2015:18:47:15 +] "OPTIONS / HTTP/1.0" 302 - "-" > > >> "-" > > >> 10.1.1.1 - - [13/Apr/2015:18:47:17 +] "OPTIONS / HTTP/1.0" 302 - "-" > > >> "-" > > >> 10.1.1.1 - - [13/Apr/2015:18:47:19 +] "OPTIONS / HTTP/1.0" 302 - "-" > > >> "-" > > >> ^C > > > > > > I have a feeling you might have been little bit confused here. Per my > > > understanding, and your configuration: > > > > > > server server10 10.1.1.10:20333 maxconn 256 *check agent-check agent-port > > > 9333 agent-inter 4000* > > > > > > the HAP is doing a health check on the agent you are using and not on the > > > Apache so the apache response in this case looks irrelevant to me. I don't > > > know how did you setup the agent since you haven't posted that part but > > > this is an excellent article by Malcolm Turnbull, the inventor of > > > agent-check, that might help: > > > > > > > > > http://blog.loadbalancer.org/open-source-windows-service-for- reporting-ser > > > ver-load-back-to-haproxy-load-balancer-feedback-agent/ > > We used this exact blog entry as our starting point. In our case, the xinetd > script compares load average, apache process count, cpu info and a little salt > to come up with a number ranging from 0% to 500%. > > > and press enter twice and check the output. Other option is using curl: > > > > $ curl -s -S -i --http1.0 -X OPTIONS http://10.1.1.12:20333/ > > [root xr1 ~]# curl -s -S -i --http1.0 -X OPTIONS http://10.1.1.12:20333 > HTTP/1.1 302 Found > Date: Tue, 14 Apr 2015 23:39:40 GMT > Server: Apache/2.2.15 (CentOS) > X-Powered-By: PHP/5.3.3 > Set-Cookie:
TLS-PSK support for haproxy?
Hi, I was wondering if HAProxy can do TLS-PSK. this cipher setting is advantageous in several scenarios, in particular with low-end clients or with stunnel backends. However, since I could not find any configuration option that denotes the preshared key, I would assume that this is not supported by HAProxy. Is TLS-PSK support? if not, it should be rather easy to implement, because it basically entails another conf option which would be passed to OpenSSL during initialization. Regards, Gil Bahat, DevOps Engineer, Magisto Ltd.
Latest design of super professional HD wearable video camera and 3G network camera
DearSiror=Madam, Hopethingsarewellwithyou. Bytheway,Wesup=ply oneof oursuper security HDcameras for=policemanwhichsellespeciallywellforyourreference.Everymonth=bsp;,weallexportover5000pcstoUSA and Europe.,welcome=yourinquiries ,thanks. OEM,ODMarebothavailalbe. Welookforwardtohearingfrom=you. BestRegardsJenny =20 ContactUS:Company Name:SmartShineTechnologyCo;Ltd.Address:2Building,Ton=gle IndustryPark ,NanshanRoad,Nanshan Industry,She=nzhen,China.Tel:008613528871-2=67Fax:008675526187082Email: pollyyuehe@h=otmail.com= info@szsmartshine.comWebsite:www.szsmartshine=.com = =20