On Wed, Nov 23, 2011 at 10:38 PM, Igor Sysoev <igor@sysoev.ru> wrote: > On Wed, Nov 23, 2011 at 10:32:27PM +0530, Fasihullah Askiri wrote: > > Sorry, I am not sure I understood you correctly. It is used in headers_in > > for look up into headers_in_hash OK. But what about headers_out? > > "lowcase_key" in headers_out may be not set if these headers are not >by faskiri.devel - Nginx Development
Your Apache is not set correctly. Please make sure that the VirtualHost is setup correctly. Basically normal wget is working but if you set the host: header apache rejects the request. I think you have explicity put a VirtualHost domain:8080 changing that to VirtualHost *:8080 should fix it. In any case, since plain wget also gives you errors, you are better off looking at Apache logs/manual thaby faskiri.devel - Nginx Mailing List - English
Hi I have a plugin that uses request.headers_out.headers, I use the lowcase_key of the element for something. However, recently while debugging a crash I noticed that the lowcase_key isnt always initialized I would have taken that as a bug but noticed that there are other places where lowcase_key isnt initialized. However, in all the three instances, header.hash is initialized to 1. So, the quby faskiri.devel - Nginx Development
Hi, Small observation, from your configuration http://subdomain.mydomain.com Will initiate a request to http://localhost:8080/subdomain/ and not http://localhost:8080/subdomain which you said works in the browser. You might want to check that out. Also, you can check out the tomcat's access logs to see what request you got. On Wed, Nov 23, 2011 at 4:52 PM, nicksoft <nginx-forum@nginx.by faskiri.devel - Nginx Mailing List - English
Thanks for your attention! It works fine with accept_mutex off, I will run my stress test harness over the weekend to see the impact on the performance. If there is a significant difference in performance, will surely update the thread with the same. For my understanding, I had implemented a workaround to get around this problem. Is your solution along the same line? My patch: diff --gby faskiri.devel - Nginx Mailing List - English
Hi Andrew Thanks for the prompt reply. As a temporary fix I had created a variable in the shared memory to track which pid is holding the mutex so that the check in works. It works fine for me, hadnt realized I could switch it off. Are we talking about putting "accept_mutex off" in the nginx.conf file? It will be great if you could explain what that will actually do, as in, how wiby faskiri.devel - Nginx Mailing List - English
Hi All I use nginx configured with multiple workers. I also have an nginx module that crashed due to an error when I noticed that the module crash leaves nginx in a state where it cannot accept new calls. Removing my module and killing the "active" worker (the one which seems to take the new request) with a SIGHUP again caused nginx to hang. Killing the other worker(s) seem to be wby faskiri.devel - Nginx Mailing List - English