Re: nginx 1.4.1 + 'gzip on' causes download of file instead of displaying it in browser

i found the bug - the web server returned in "Content-Type" header just "text/html" and not added "charset=UTF-8". why text/html is not enough ? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239608,239622#msg-239622 ___ nginx mailing list ng

nginx 1.4.1 + 'gzip on' causes download of file instead of displaying it in browser

when i use nginx 1.4.1 + 'gzip on', once in every 2 requests i get the index.php (which its output is text/html) being downloaded by the browser as unknown file type instead of displayed in it (the broswer displays the "download & save" window and writes in this window that its content type is 'app

Re: which version to use in production - 1.2.x or 1.3.x

thanks, where can i see the API changes between 1.2.x and 1.3.x ? i currently use subrequest in 1.2.8 and in 1.3.16 the filter module is not called and the browser waits forever (so it does not go to backend also) Posted at Nginx Forum: http://forum.nginx.org/read.php?2,238512,238573#msg-238573

how to debug memory leak/grow

in my nginx, compiled with my modules, i see that under every day usage (its on a web site , i cannot reproduce this in my lab) the memory usage of nginx grows all the time, it has many open connections (but the total number of connections is high but stays roughly the same over time) and aftert a

which version to use in production - 1.2.x or 1.3.x

i know that 1.3.x is development version, but is it stable enough to be used in production? as stated here: http://forum.nginx.org/read.php?2,221377,221390#msg-221390 Tell me if i figured that right : if the 1.2.x is based on 1.2.0 - then its basic functionality is about 1 year old, and the main c

using upstream module that won't override the original request

I'm trying to hold a client request to backend (not go to the server yet), issue an upstream request to another server, then parse the upstream response, store it in my orig. request ctx, only then go to backend server (original request), and in the output filter inject some of the ctx data i store

Re: nginx + my module crashes only when ignore client abort = on

after a few addons to the code - in totally irrelevant places - the error returns so it did not help. Now i try to create a new upstream handler so i can use it instead of the subrequest model. i described the model i work in the first post above. let me add this: in my first tests of the upstrea

Re: nginx + my module crashes only when ignore client abort = on

i changed to pcalloc as you told me and the crash seems to be solved !! thanks alot Gad Posted at Nginx Forum: http://forum.nginx.org/read.php?2,237362,237488#msg-237488 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/

Re: nginx + my module crashes only when ignore client abort = on

> Note though, that by changing headers_in structure you are > responsible for it's consistency. It's usually much better idea > to use upstream functionality to create needed request to an > upstream instead (proxy_set_body, proxy_pass_headers and so on). > but can i wait for the upstream to

Re: nginx + my module crashes only when ignore client abort = on

thanks Maxim ! i very appreciate your help on this. about the temp file - i protect from a response to be written to a file by knowing the max size that can be sent by the server and enlarging the proxy buffers accordingly. i know i ruin the original request header - its the main purpose for my cod

Re: nginx + my module crashes only when ignore client abort = on

more info: when i use "ignore client abort = on" , the crash happens when the client aborts the connection, BEFORE my subrequest handler is called, so its unlikely this code causes the crash. also, i send the subrequest to a configured url named "aaa_post/" which uses the proxy module to send it to

Re: nginx + my module crashes only when ignore client abort = on

Ok, i'll attach my calling to subrequest code, its working flawlessly except the case i reported here: //-- /* Note: the purspose of this code is to call a handler module (at rewrite phase), send special POST subrequest to another serv

Re: nginx + my module crashes only when ignore client abort = on

thanks after i get the subrequest response in a handler function i registered, what can i do in order to tell the ngin core the subrequest had finished ? in my case i do only these actions: ngx_http_core_run_phases(r->main); return NGX_OK; is this ok ? BTW, its not a case of a client body, i

Re: nginx + my module crashes only when ignore client abort = on

i attache here my "debug_http" log - note that "http finalize request" is called twice (i think that one of them nulls the connection so nulls its log too), and thats NOT happening when NOT using proxy_ignore_client_abort: btw: i use proxy http version 1.1, if it helps ---

nginx + my module crashes only when ignore client abort = on

i use nginx ver 1.2.5 (also tried 1.2.7) with my module that sends subrequest to an upstream, waits untill response get back, then goes to backend upstream and fetch the regular web page from it. when i add to nginx conf "proxy_ignore_client_abort on;", nginx crash with signal 11 (seg fault) when i