Ok, thx you for answering. Regards, Bertrand On Mon, Dec 3, 2012 at 2:55 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Sun, Dec 02, 2012 at 12:15:03PM +0100, Bertrand Paquet wrote: > > > Hi, > > > > I have virtual machine running on qemu / kvm. > > > > cat /proc/cpuinfo give : > > processor : 0 > > vendor_id : GenuineIby bpaquet - Nginx Mailing List - English
Hi, I have virtual machine running on qemu / kvm. cat /proc/cpuinfo give : processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 2 model name : QEMU Virtual CPU version 1.1.2 stepping : 3 microcode : 0x1 cpu MHz : 1999.999 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr ssby bpaquet - Nginx Mailing List - English
Hi On Sun, May 6, 2012 at 11:02 AM, agentzh <agentzh@gmail.com> wrote: > On Fri, May 4, 2012 at 10:09 PM, Bertrand Paquet <bpaquet@octo.com> wrote: > > I'm glad to annouce the V0.2 of the Enhanced Memcached Nginx module. > > > > Based on the standard Memcached Nginx module, this module offers > following > > extras features : > > Thanks for sharingby bpaquet - Nginx Mailing List - English
Hi all, I'm glad to annouce the V0.2 of the Enhanced Memcached Nginx module. Based on the standard Memcached Nginx module, this module offers following extras features : * Send custom http headers, like `Content-Type`, `Last-Modified`. Http headers are stored in memcached, with your body data. * Hash keys to use large keys (> 250 chars, memcached limit) * Store data into memcached, via HTTP rby bpaquet - Nginx Mailing List - English
Hi, Does your application server fill memcached correctly ? May be a binary / encoding problem when connecting to memcached. Or the content is stored gzipped ? Regards Bertrand On Sun, Apr 22, 2012 at 19:02, Jakub Å krha <serga@seznam.cz> wrote: > ** > Hi, > > I have problem with nginx and memcached responses such as text/html or > application/json and I will be glad forby bpaquet - Nginx Mailing List - English
Hi all, Finally, I do not use subrequest, I write the following code, inspired from upstream module. I call ngx_http_upstream_send_another_request from process_header. It's working fine. Feel free to comment my code, if you think I can have problem, memory allocation, segfault or others. Regards, Bertrand static void ngx_http_upstream_send_another_request_dummy_handler(ngx_http_request_t *r,by bpaquet - Nginx Mailing List - English
Hi, Arg, it's not a good news :) Do you think I can do ngx_http_subrequest to do some additional request to back end ? How to say to nginx to wait for subrequest before calling create_request ? Regards, Bertrand On Mon, Jan 16, 2012 at 22:20, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Mon, Jan 16, 2012 at 09:40:26PM +0100, Bertrand Paquet wrote: > > > Hby bpaquet - Nginx Mailing List - English
Hi all, I'm trying to write an upstream which have to do multiple request / reply with backend, for one frontend request. Currently, - I'm writing first request to backend in create_request handler, write data into r->upstream->request_bufs, and returning NGX_OK - Nginx call me on process_header. I can read data from r->upstream->buffer. I can loop on process_header if I return NGX_Aby bpaquet - Nginx Mailing List - English