When I try it out, the definition that comes later seems to take effect. The
question is, are there unintended consequences of doing this?
http {
map $http_host $a {
hostnames;
default 1;
example.com 1;
*.example.com 2;
}
map $http_host $a {
host
Hello!
On Thu, Apr 11, 2013 at 11:08:47AM -0400, winniethepooh wrote:
> Maxim Dounin Wrote:
> ---
> > Hello!
> >
> > On Thu, Apr 11, 2013 at 04:15:02AM -0400, winniethepooh wrote:
> >
> > It's not clear why you added "x.x.x.x" to the upstream
On 11 Apr2013, at 05:43 , AJ Weber wrote:
> yum repolist -v nginx
> Loading "fastestmirror" plugin
> Config time: 0.019
> Yum Version: 3.2.29
> Loading mirror speeds from cached hostfile
> * base: centosp4.centos.org
> * extras: centosc5.centos.org
> * updates: centosy3.centos.org
> Setting up P
Maxim Dounin Wrote:
---
> Hello!
>
> On Thu, Apr 11, 2013 at 04:15:02AM -0400, winniethepooh wrote:
>
> It's not clear why you added "x.x.x.x" to the upstream block if
> it's not an upstream but the same server. Obvious solution would
> be to
Hello!
On Wed, Apr 10, 2013 at 04:57:33PM -0400, abstein2 wrote:
> I can't find documention anywhere on what it means when nginx shows 001 as
> the value of $status in the access_log.
>
> I currently use nginx as a reverse proxy and I get this error when uploading
> large files (2+ MB though my
On Wed, Apr 10, 2013 at 11:47:24PM -0400, mengqy wrote:
> nginx 1.3.15, ubuntu 12.04, bash:
>
> $ ./configure --prefix=~/tools/webserver/install ...
> $ make && make install
>
> --> a dir named '~' is created within current dir, but `~` should be
> interpreted as `$HOME` instead, right?
>
> Than
Hello!
On Thu, Apr 11, 2013 at 04:15:02AM -0400, winniethepooh wrote:
> I'm trying to use the Dropbox public folder and my nginx server as a
> upstream server to server static files. I'm hoping someone can point me in
> the right direction or tell me what I'm doing wrong.
>
> So:
> my.domain.net
Hello!
On Thu, Apr 11, 2013 at 06:18:19PM +1200, Steve Holdoway wrote:
> Hi Folks,
>
> I've got a magento site under development, and just want it to be
> password protected until it goes live. No problem I thought...
>
> add in the auth_basic/auth_basic_user_file entries to the location /
> bl
I'm trying to use the Dropbox public folder and my nginx server as a
upstream server to server static files. I'm hoping someone can point me in
the right direction or tell me what I'm doing wrong.
So:
my.domain.net/u/#/*.bz2 serves from
http://dl.dropbox.com/u/#/*.bz2 "twice" as mu