Hello - Working with SPDY/47 and Lua to do a location.capture that ultimately calls fastcgi. The same setup does not produce an issue within http or TLS only server configs, but bails once the spdy flag is added. Doesn't appear to be related to the known SPDY limitations. nginx version: nginx/1.3.3 built by gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) TLS SNI support enabled configure arguments: --by gregr401 - Nginx Development
Hi - Try the following: root /var/www/$http_host;by gregr401 - How to...
HI! Try adding the following to your config: proxy_set_header Host $http_host; You're current config is not passing back the original users http_host header, so you're backend config leveraging the default vhost. Enabling the above config line will maintain the original header through the proxy_pass and allow your backend vhosts to react accordingly. There are a number of other proxyby gregr401 - How to...
Hi! How is your vip configured, can you share some more details? High-level, I would double check that nginx is listening across both interfaces per server (localhost + vip). This really isn't a nginx issues as much as it is properly configuring your vip and failover mechanism. Would need much more details around that layer to help troubleshoot further. Good luck!by gregr401 - How to...
Wouldn't '*' match 200, 301, 302, etc... :) Better to be precise and explicit.by gregr401 - Nginx Mailing List - English
Did that rev actually compile and make without issue for you? I was using that module a while back and ended up commenting out the below line inorder for it to build successfully. /* static ngx_str_t ngx_http_redis_db = ngx_string("redis_db"); */ I wasn't using different redis db's at the time and didn't look into it much. I bet pipelining with agentzh's redis2 would work justby gregr401 - Nginx Mailing List - English
Well, all this seems to be tracked back to an env issue on my side, argh. I ended up setting a lua_package_cpath and now parsing replies is working exactly as they should (interesting that some other features were working, tho, hmmm). Thanks again for the above help and validation agentzh and logar! nginx + redis pipelining + lua FTW =)by gregr401 - Nginx Mailing List - English
Thanks, logar. I mimicked your test config and the below is the result: location /testluaparser { content_by_lua ' local replies = ngx.location.capture("/redis2") local parser = require("redis.parser") ngx.say("reply status is:",replies.status) ngx.say("reply body is:",replies.body) ngx.say("end of showreby gregr401 - Nginx Mailing List - English
Thanks for the responses! Everything on the redis end is fine and I am expecting the raw responses by leveraging your redis parser, it's within the parser examples I'm not making any progress. I'd like to be able to parse out and set each value to a variable. Here's my test locations and log snippet, hopefully I'm just missing something obvious :) ## redis auth is off at this point, just trby gregr401 - Nginx Mailing List - English
Hi Folks - Looking for some examples or hints in order to leverage lua_parser && redis2. To date, I've been using httpredis and content_by_lua code to perform a number of simple 'get's which has worked well. Now, I'd like to pipeline a number of redis requests together in order to leverage 'auth' within redis and eventually pipeline numerous 'get's at once. This is what I have workby gregr401 - Nginx Mailing List - English
How many uri / backend mappings do you have? You could perform the above in two straight forward location blocks, based on the uri. location /abc { proxy_pass http://host01:8080; } ....by gregr401 - Nginx Mailing List - English
Oops, that 'server 80 {' line above is completely incorrect :) Take note...by gregr401 - Nginx Mailing List - English
I'm sure there are a few different ways to accomplish this, personally I'm working on a dynamic method to perform this with a mysql backend. For a more simplistic method, maybe try using a map hash for the backend_server variable that is matched against the incoming $http_host: map_hash_bucket_size 64; map $http_host $backend_server { hostnames; defaultby gregr401 - Nginx Mailing List - English