trying to use nginx's built-in perl stuff... here's an example. any clue why this doesn't work? in /etc/nginx/nginx.conf: http { perl_modules /etc/nginx/perl/lib; perl_require Foo.pm; server { listen 80; server_name hostname.com; location / { perl Foo::handler; } } }by mike - Nginx Mailing List - English
On Mon, May 11, 2009 at 11:21 AM, Payam Chychi <pchychi@gmail.com> wrote: > How does your proxy config look like? have you read the wiki site at all? > http://wiki.nginx.org/NginxHttpProxyModule Yes, I know what the wiki site is, I'm the one who suggested the address even. It's not an issue of nginx configuration, it's asking for the Apache counterpart. The other person alreby mike - Nginx Mailing List - English
that was it. thanks. On Mon, May 11, 2009 at 11:16 AM, Swish <swish@latouraineinc.com> wrote: > You can use mod_rpaf (Reverse Proxy Add Forward Module) > http://stderr.net/apache/rpaf/ > > I'm doing this currently with no problems. > > On Mon, May 11, 2009 at 10:57 AM, Michael Shadle <mike503@gmail.com> wrote: >> In apache I want that to be the REMOTE_by mike - Nginx Mailing List - English
In apache I want that to be the REMOTE_ADDR, essentially. This is like nginx's set_real_ip_from. I am pretty sure Apache has it and I'm sure people on this list have used it.by mike - Nginx Mailing List - English
I wouldn't see what someone has to gain registering all 3 domains and putting up a wiki instead of a linkfarm. I almost regged php-fpm.org a while ago heh. On May 7, 2009, at 6:01 AM, "Jim Ohlstein" <nginx-forum@nginx.us> wrote: > > Nickolas Daskalou Wrote: > ------------------------------------------------------- >> Nice zipcode and phone number too.by mike - Php-fpm Mailing List - English
Andrei, are you out there? You should make it required for people to register, that will cut out the majority of spam. I can do it for you (I manage the drizzle.org wiki) I'd be more than happy to help host it or whatever you need. FYI: I'm going through just reading stuff and trying to revert back pages to their last non-spam version On Wed, May 6, 2009 at 2:26 PM, Michael Shadle <by mike - Php-fpm Mailing List - English
Yeah, I did not mean to start a flame war. Obviously this will bring up the religious windows vs. linux/unix. I just found it quite interesting so many people were interested and seemed to be expecting the native Windows release. I do slightly disagree though. Sure, a developer might not have OS selection options and the system administrator ultimately makes the call, butif you're able toby mike - Nginx Mailing List - English
well at the moment i am waiting for the current developer (that i am paying) to finish it to a "complete" enough state and then let the community mature it and hack it up, maybe have igor take a look and correct any possible things that might make nginx unhappy. the developer knows C but is not fluent in either nginx or kerberos, so he's doing a trial by fire. the one thing i wanby mike - Nginx Mailing List - English
I mean.... really? If you're looking for performance, is Windows really your target OS? and security? Not to mention things like php-fpm don't exist... I've been surprised at the demand for nginx on Windows. I figure people running nginx are looking for a high performance solution, and why anyone would run Windows for python/perl/php/fastcgi stuff makes me very confused. I'd only runby mike - Nginx Mailing List - English
well it's registered in andrei's name. so that is promising. On Tue, May 5, 2009 at 9:20 AM, Jim Ohlstein <nginx-forum@nginx.us> wrote: > > I hadn't seen the Wiki before either. > > > > domain: php-fpm.com > reg_created: 2009-01-14 08:05:09 > expires: 2010-01-14 08:05:09 > created: 2009-01-14 09:05:10 > changed: 2009-01-14 18:14:36 > transfer-prby mike - Php-fpm Mailing List - English
I never even knew someone registered it. I was thinking of registering a domain for it but then thought once it goes into mainline php (hopefully) it's moot. On May 5, 2009, at 12:28 AM, Dai <paolo.rodriguez@acceliria.com> wrote: > > Hi, > > Can something be done to stop the spamming on the wiki? Particularly > the page http://php-fpm.com/wiki/Features is unusaby mike - Php-fpm Mailing List - English
nevermind. i think this might be working now. maybe i had something else going on. ignore me :) On Mon, May 4, 2009 at 1:34 AM, Michael Shadle <mike503@gmail.com> wrote: > 2009/5/4 Igor Sysoev <is@rambler-co.ru>: > >> Regexs in server names are run in order of their appearence. > > are you sure? i tried different order and it still matched the same defauby mike - Nginx Mailing List - English
i am working on hostname based regexs, not location based ones... On Mon, May 4, 2009 at 1:29 AM, Delta Yeh <delta.yeh@gmail.com> wrote: > How about location block? Merged or in order of their appearence > > i.e. > > location /aa { > conf1 > } > location /bb { > conf2 > } > location /aa { > conf3 &gby mike - Nginx Mailing List - English
2009/5/4 Igor Sysoev <is@rambler-co.ru>: > Regexs in server names are run in order of their appearence. are you sure? i tried different order and it still matched the same default one.by mike - Nginx Mailing List - English
The first one always gets matched. Is there a way to make nginx use the one that matches the best? i.e. foo123.mike.bar.com should go to #2 foo.mike.bar.com should go to #2 blah.mike.bar.com should go to #1 etc. i've tried in opposite order but it seems that it always sides with the more generic one, which does make sense i suppose but perhaps there is a way around it? thanks.by mike - Nginx Mailing List - English
On Sun, May 3, 2009 at 5:56 PM, Jim Ohlstein <jim.ohlstein@gmail.com> wrote: > Correct me if I'm wrong, but you still have to put > > location ~ \.php$ { > fastcgi_pass 127.0.0.1:9000; > > ... > } > > for each server block where you want to configure php. Even if you are able > to put the fastcgi_pass directive into fastcgi_paraby mike - Nginx Mailing List - English
On Sun, May 3, 2009 at 5:06 PM, Mathew Davies <thepixeldeveloper@googlemail.com> wrote: > location ~ \.php$ > { > fastcgi_pass 127.0.0.1:9000; > fastcgi_index index.php; > fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; > include fastcgi_params; > } > } You can put these in fastcgi_params: fastcgi_index index.php; fastcgi_param SCRIby mike - Nginx Mailing List - English
This will work seamlessly with bugzilla? Also we have a strict policy with not modifying the source package for easy upgrades. I'm sure somehow you could hack this kind of support into bugzilla but that would be a lot of modification. On May 1, 2009, at 7:10 PM, luben karavelov <luben@unixsol.org> wrote: > Michael Shadle wrote: >> I am coming from the camp where I caby mike - Nginx Mailing List - English
I am coming from the camp where I cannot alter the application. Coding one from scratch sure you can impelement an fcgi interface. On May 1, 2009, at 5:43 PM, luben karavelov <luben@unixsol.org> wrote: > Michael Shadle wrote: >> If it has to be perl, I'd say look into using fcgiwrap. >> > > You will get performance like CGI (new process started on every &by mike - Nginx Mailing List - English
On Fri, May 1, 2009 at 12:00 AM, Tristan Griffiths <tristan.griffiths@stomp.com.au> wrote: > http { > server { - listen 192.168.1.1:80 default; + listen 80 default; > } > } try that also you could try dropping default. maybe the behavior will change. i guess it depends if nginx will listen on new ips that are inherited through heartbeaby mike - Nginx Mailing List - English
2009/4/30 Igor Sysoev <is@rambler-co.ru>: > server_name ~... > > set $name $1; > > root /....$name; server { listen 80; index index.php index.html; server_name ~^foo(.+)\.mike\.bar\.com$; set $name $1; root /home/mike/web/foo$name; include /etc/nginx/defaults.by mike - Nginx Mailing List - English
2009/4/30 Igor Sysoev <is@rambler-co.ru>: > The "break" after "return" costs nothing, but useless. > Also, it' better to combine all check in single regex - it will be run > much faster: > > if ($http_user_agent ~* "googlebot|looksmart|...") { > return 404; > } Thanks for the pointers. Originally I was doing it one at aby mike - Nginx Mailing List - English
i thought nginx listened on port 80 by default. couldn't you just not explicitly define it? On Thu, Apr 30, 2009 at 11:26 PM, Tristan Griffiths <tristan.griffiths@stomp.com.au> wrote: > Greetings. > > We would like to setup our Nginx instances in a HA pair. Using > Heartbeat, we have Nginx listening on virtual addresses on the active > server. > > On the passby mike - Nginx Mailing List - English
2009/4/30 Igor Sysoev <is@rambler-co.ru>: > include /etc/nginx/expires.conf; > > this "html" is captured. yep # cat expires.conf location ~* \.(jpg|jpeg|gif|css|png|js|ico|html)$ { expires max; access_log off; } so ... how can i use root captures but still have these other options? make a location / {} block and then put theby mike - Nginx Mailing List - English
sorry, that was supposed to be bar.com - i just messed up substituting 2009/4/30 Igor Sysoev <is@rambler-co.ru>: > First, "~^foo(.*?)\.bar\.ssgisp\.com$" will never match "foo2.mike.bar.com". > Second, "~^foo(.*?)\.bar\.com$" will capture "2.mike" with "foo2.mike.bar.com". You're right though, something in the files is messingby mike - Nginx Mailing List - English
For my purposes, I want it to authenticate against a KDC/LDAP/AD server, whatever it is. I think it's a Windows 2003 based network. But sure, I'll shoot to to you too. Remember it is very alpha and I think he said it can crash and he's trying to fix that. On Thu, Apr 30, 2009 at 8:28 PM, Andrew Deason <adeason2@uiuc.edu> wrote: > On Wed, 29 Apr 2009 02:30:52 -0700 > Michaelby mike - Nginx Mailing List - English
i have this, which seemed like it would work according to my attempt just a week ago... server { listen 80; index index.php index.html; server_name ~^foo(.*?)\.bar\.ssgisp\.com$; root /home/mike/web/foo$1; include /etc/nginx/defaults.conf; include /etc/nginx/development.conf; include /etc/nginx/expires.conf; location ~ \.pby mike - Nginx Mailing List - English
If it has to be perl, I'd say look into using fcgiwrap. Otherwise, use PHP. It's slim enough and very easy to deploy and proxy to using nginx. On Thu, Apr 30, 2009 at 11:46 AM, Mark Aiken <maiken@niftybrick.com> wrote: > Hello, > > My apologies for the newbie question; I have poked around quite a bit > and can't find a definitive answer. > > I'm planning to useby mike - Nginx Mailing List - English
Yes, I believe it has to be on the domain currently. However, I would -love- for it to not have that requirement. I will send the code to you separately and you can give it a go. It sounds like you have better understanding of how this stuff works. Of course, I don't know if your company's implementation differs from mine (it's a Windows 2003 Active Directory based off LDAP and supporby mike - Nginx Mailing List - English
basically this: http://wiki.nginx.org/RedHatNginxInitScript just adds an extra macro/function in there to do an nginx -t $conffile, and adds it in appropriate places (reload, restart, start, now upgrade as well) also we had to add in a sleep inside of restart restart() { configtest || return $? stop sleep 3 start } however, i suppose depending on the signal thatby mike - Nginx Mailing List - English