Thanks guys for your replies. I have previously looked at how NGX_AGAIN is handled in the nginx source, and its along the lines of if ngx_http_read_client_request_body returns anything other than NGX_OK, return that from the module, otherwise return NGX_DONE. The problem is when I do this, my module is never called again. @Mike: I have tried what you described and it it promising in the sense tby sayeo87 - Nginx Mailing List - English
I am trying to develop a handler module in Nginx 0.7.59 to intercept POST requests and perform internal redirections based on the values in the POST data. The problem is, on larger POST requests (~ > 2KB), ngx_http_read_client_request_body() sometimes returns NGX_AGAIN instead of NGX_OK. I have read at various places that if one receives any other status than NGX_OK that that the module shouldby sayeo87 - Nginx Mailing List - English
In Nginx 0.6.37, when I get a POST request, and put it through a 404 error_page directive, when it reaches the next location the POST data is lost. I also tried a rewrite instead, like: if (!-e $request_filename) { rewrite ^/(.*) /proxy$uri last; and that yields the same result. Will using the internal location redirect using the "@" symbol work in this case? If it does I willby sayeo87 - Nginx Mailing List - English
Also wondering, in the new nginx dev versions with the new built-in caching methods, is there any way to get POST arguments there?by sayeo87 - Nginx Mailing List - English
In nginx 0.6.37, is there any way at all to get the arguments of a POST request? I've seen that this doesn't work with static files, but is there any way to structure the POST request such that I can grab the arguments in my nginx server? Thanks!by sayeo87 - Nginx Mailing List - English
Arrgghh......... so, I found out that some things are bugged within 0.6.32 so I installed 0.6.37 from source. After configuring everything, the same problem is occuring- ie: memcaching does not work. Here are my configs. Any help is much appreciated. /usr/local/nginx/conf/nginx.conf user www-data; worker_processes 1; error_log logs/error.log; #error_log logs/error.log notice; #eby sayeo87 - Nginx Mailing List - English
I solved the problem. It was because I didn't edit my /etc/nginx/sites-available/default file to include the new information. So many tutorials didn't mention that you have to edit this file! =(by sayeo87 - Nginx Mailing List - English
Hi, I think I'm having trouble even getting the most basic case of Nginx+memcached working properly. Here is my /etc/nginx/nginx.conf file: user www-data; worker_processes 1; error_log /var/log/nginx/error.log; pid /var/run/nginx.pid; events { worker_connections 1024; } http { include /etc/nginx/mime.types; default_type application/octet-stream;by sayeo87 - Nginx Mailing List - English