Is anyone else amazed at how many people use nginx on Windows?

郭振立 [email protected],
Why not use virtual machine to run nginx as a reverse proxy ?

Igor,

I agree that you don’t need to spend too much time on windows port.

Keep focus and succeed.

2009/5/7 郭振立 [email protected]

“Michael S.” [email protected] wrote on Wednesday, May 06, 2009 at
2:37 PM:

me very confused. I’d only run Windows if I needed .NET/ASP/something
Windows-y.

Oh well :slight_smile:

Personally, a native build of nginx on Windows is interesting to me.
There
are no good, small native httpds which are capable of IPv6 at this time.
As
I don’t do Cygwin, that version was uninteresting to me. I was looking
into
the feasibility of getting it to run under either UWIN and/or Interix
(aka
SFU/SUA), as those are my normal POSIXy environments on Windows
machines. I
have a number of Windows machines that I occasionally want to put static
content on, which only are reachable via IPv6, and IIS is seriously too
heavy for static content. So, if Igor’s build works, and well, I’m all
for
it. Of course, it’d be better if we could build it ourselves for any
customizations which one would like, but meh.

Anyhow, that’s my 2 cents, whatever they’re worth in the current global
economy.

Warmest,

–Matt

In my case, I do the majority of web development testing on my local pc
prior to pushing it to a production server.
It is useful to have a similar server setup locally as to what you will
be using full scale and in that regard a native implementation of nginx
is very helpful.

I personally don’t care to run VMs 24/7 just to run a local web server
for testing. Again I appreciate the ability to have a similar server
setup locally as to what I use on my *nix box, so using IIS/Apache by
themselves doesn’t really help my cause. Therefor whatever improvements
Igor does regarding the windows buids are very much appreciated by
myself and I’m sure many others.

Posted at Nginx Forum:

I’m just a lurker so far, but this issue may impact the future of nginx,
which I do care about so I’ll give this a shot. Feel free to disregard
this if you wish.

I am with others who think that a Windows port of nginx may be useful,
but Igor should NOT spend too much time on it. Ok, I lie. I think
Windows port should be left outside of the primary nginx effort.

Unless of course, he has some agenda or commercial purpose behind it.
For that, I think no one should interfere with that decision, although I
personally think that building commercial company using nginx under
opensource platform is a better alternative.

nginx is a wonderful piece of software. We are thankful for that…

With that said, I really can’t think of a way why nginx should natively
support Windows. Most people here use it for testing and web
development. (Or are there big sites out there running nginx under
Windows?)

A lot of people appreciate the small memory footprint and use nginx for
development platform. I myself have created VMware image loaded with
nginx and WordPress for WP developers and written an article on how to
setup nginx on Windows for testing WordPress.

But let’s think about it. What nginx is REALLY for?

I think nginx is a great software to build high traffic web servers, and
other features that I haven’t used yet. And by porting to Windows
natively, this wastes time that otherwise could be used to further
improve nginx in this direction.

There are still a lot of sites that could have saved a lot by migrating
to nginx. As nginx grows, people will be attracted to the stability and
features added by the software. It is a much BETTER idea to focus on
this instead of serving a need for Windows users, which account for a
small portion of the nginx community, not to mention that it was not
what it was designed to be.

Developing for Windows can only slow things down. And I think this is a
BAD decision. Nginx can’t satisfy everyone, nor should it try to. At
least the time has not come yet for that kind of expansion. Let me
elaborate.

Satisfying some developers who want to save a bit of memory under
Windows will only hurt the software in the long run because like it or
not this list has to support the whole new beast. That’s (close to) a
full time job, I think.

That’s my 2 cents…

My goodness. I agree, this was a legitimate question/statement on Mike’s
part. I’ll admit I am surprised. I use Windows on my desktop machine to
run some native Windows apps for my business. I also run Linux on the
same box for lots of other things. My laptop is a MacBook Pro. All of my
servers run Linux. It works best for my purposes at this time. If I were
to start over I might use FreeBSD but that’s a war I don’t want to start
on this list. It would, however, make the crowd in Redmond happy to see
people fighting over *nix system choices, yet some would call you an
“idiot” for choosing Linux over BSD for an OS.

Calling someone “an idiot” for their choice of technology is like
calling someone an idiot for their politics or for their religion.

The is clearly a demand for a Windows version. Igor is developing it
for his own reasons. Unless you are signing his paychecks, the only
“vote” that counts is Igor’s.

Posted at Nginx Forum:

Moving another apache server to nginx :slight_smile:

Can I get some help with this rewrite??

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/index.php
RewriteCond %{REQUEST_URI}
(/|.php|.html|.htm|.feed|.pdf|.raw|/[^.])$ [NC]
RewriteRule (.
) index.php
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]

On Wed, May 13, 2009 at 11:13:21PM -0500, AMP Admin wrote:

Moving another apache server to nginx :slight_smile:

Can I get some help with this rewrite??

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/index.php
RewriteCond %{REQUEST_URI} (/|.php|.html|.htm|.feed|.pdf|.raw|/[^.])$ [NC]
RewriteRule (.
) index.php
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]

location = /index.php {
fastcgi_pass …;
}

location ~ (/|.php|.html?|.feed|.pdf|.raw|/[^.]+)$ {
try_files $uri $uri/ /index.php;

   fastcgi_pass    ...;

}

On Wed, May 13, 2009 at 11:18:39PM -0500, AMP Admin wrote:

allow from all

Probably you need just

location ~ .inc$ {
deny all;
}

because .php will be handled by fastcgi only.

Hello! I have a question.

I’m trying to set up Nginx to forward my old domain to my new domain.
waterfortheoppressed.com => wfto.cc. But I not only need it to forward
it,
I need the persons browser address to change to wfto.cc. I’ll provide
the
working Apache example here:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(waterfortheoppressed.com) [NC]
RewriteRule ^(.*)$ http://www.wfto.cc$1 [R=301,L]

RewriteCond %{HTTP_HOST} ^(www.waterfortheoppressed.com) [NC]
RewriteRule ^(.*)$ http://www.wfto.cc$1 [R=301,L]

Thanks for any help you may have.

Oh and one more please!!!

DirectoryIndex index.php

<FilesMatch “.(php|inc)$”>
Order allow,deny
deny from all

<FilesMatch “(index.php|dl.php|ut.php|lt.php|download.php)$”>
Order allow,deny
allow from all

Hello Claude,

Thursday, May 14, 2009, 9:23:55 PM, you wrote:

Hello! I have a question.

I’m trying to set up Nginx to forward my old domain to my new domain.
waterfortheoppressed.com => wfto.cc. But I not only need it to forward it,
I need the persons browser address to change to wfto.cc. I’ll provide the
working Apache example here:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(waterfortheoppressed.com) [NC]
RewriteRule ^(.*)$ http://www.wfto.cc$1 [R=301,L]

RewriteCond %{HTTP_HOST} ^(www.waterfortheoppressed.com) [NC]
RewriteRule ^(.*)$ http://www.wfto.cc$1 [R=301,L]

Thanks for any help you may have.

server {
listen 80;
server_name www.waterfortheoppressed.com
waterfortheoppressed.com;
# staff
}

server {
listen 80;
server_name _;

   location / {
          rewrite ^ http://www.wfto.cc$request_uri? permanent;
   }

}

On Thu, May 14, 2009 at 09:38:49PM +0700, Denis F. Latypoff wrote:

   listen 80;
          rewrite ^ http://www.wfto.cc$request_uri? permanent;
   }

}

Vice versa:

server {
listen 80;
server_name www.waterfortheoppressed.com
waterfortheoppressed.com;

    rewrite ^ http://www.wfto.cc$request_uri? permanent;

}

server {
listen 80;
server_name www.wfto.cc;

    # staff

}

Thank you very much, will try to get this working now.

2009/5/14 Denis F. Latypoff [email protected]

Hello! I have a question.
RewriteRule ^(.*)$ http://www.wfto.cc$1 [R=301,L]
# staff

server {
Denis mailto:[email protected]

Vince
Lombardihttp://www.brainyquote.com/quotes/authors/v/vince_lombardi.html

  • “We didn’t lose the game; we just ran out of time.”

Firefox says: REDIRECT LOOP Firefox has detected that the server is
redirecting the request for this address in a way that will never
complete.

lol.

It’s only when I use www.wfto.cc, and not wfto.cc.

Figured it out while writing this e-mail. Make sure that when you use
those
rewrite rules that you actually have a server named www.whatever.com, or
it
will end up in a redirect loop.

Thanks again,

Claude

On Thu, May 14, 2009 at 6:12 PM, Claude B. [email protected] wrote:

Hello Claude,

working Apache example here:
server {
location / {

That was additional homework for Claude :slight_smile:

Vince Lombardihttp://www.brainyquote.com/quotes/authors/v/vince_lombardi.html - “We didn’t lose the game; we just ran out of time.”

Don Marquis
http://www.brainyquote.com/quotes/authors/d/don_marquis.html

  • “Procrastination is the art of keeping up with yesterday.”

Hello Igor,

Thursday, May 14, 2009, 9:56:19 PM, you wrote:

On Thu, May 14, 2009 at 09:38:49PM +0700, Denis F. Latypoff wrote:

   listen 80;
          rewrite ^ http://www.wfto.cc$request_uri? permanent;
   }

}

Vice versa:

server {
listen 80;
server_name www.waterfortheoppressed.com
waterfortheoppressed.com;

    rewrite ^ http://www.wfto.cc$request_uri? permanent;

}

server {
listen 80;
server_name www.wfto.cc;

    # staff

}

That was additional homework for Claude :slight_smile: