`location = /abc {}` matches the exact uri `/abc`

`location ~ /abc` is a regex match on the uri, meaning any uri containing `/abc`,
you probably want: `location ~ ^/abc` for the uri begining with `/abc`
instead

In my app I have a `BroadcastReceiver` that is launched as a component through a `&lt;receiver&gt;` tag, filtering `android.net.conn.CONNECTIVITY_CHANGE` intents.

My goal is simply to know when a Wifi connection was established, so what I am doing in `onReceive()` is this:

    NetworkInfo networkInfo = intent.getParcelableExtra(ConnectivityManager.EXTRA_NETWORK_INFO);
    if(networkInfo.getType() == ConnectivityManager.TYPE_WIFI &amp;&amp; networkInfo.isConnected()) {
        // Wifi is connected
    }

It works fine, but I always seem to get two identical intents within about one second when a Wifi connection is established. I tried to look at any info I could get from the intent, the `ConnectivityManager` and `WifiManager`, but I can&#39;t find anything that distinguishes the two intents.

Looking at the log, there is at least one other `BroadcastReceiver` that also receives the two identical intents.

It is running on a HTC Desire with Android 2.2

Any idea why I seem to get a &quot;duplicated&quot; intent when Wifi connects or what the difference between the two might be?

CONNECTIVITY_ACTION intent received twice when Wifi connected

I want to start 100 processes in `bash`, but the `for` statement doesn&#39;t seems to like the `&amp;` symbol and I&#39;m getting a syntax error, here is what I have so far:


    echo &quot;Spawning 100 processes&quot;
    for i in {1..100}
    do
        ./my_script.py &amp;
    done

**EDIT:** I was copypasting this code, that&#39;s why the `&amp;` char was illegal.

How to start multiple processes in Bash

What is the difference between:

     location = /abc {}

and

     locaton ~ /abc {}



Nginx location matches

What is the difference between:
<pre><code class="hljs language-ini"> location = /abc {}
</code></pre>
and
<pre><code class="hljs language-bash"> locaton ~ /abc {}
</code></pre>

I am trying to proxy a request to different targets depending on an environment variable. My approach was to put the target url into the custom variable $target and give this to proxy_pass. 

But using a variable with proxy_pass doesn&#39;t seem to work. This simple config leads to a &quot;502 Bad Gateway&quot; response from nginx.

    server {
      listen   8080;
      server_name  myhost.example.com;
      access_log  /var/log/nginx/myhost.access.log;
      location /proxy {
        set $target http://proxytarget.example.com;
        proxy_pass $target;
      }
    }

The same config without the variable works:

    server {
      listen   8080;
      server_name  myhost.example.com;
      access_log  /var/log/nginx/myhost.access.log;
      location /proxy {
        proxy_pass http://proxytarget.example.com;
      }
    }

Is it really not possible to use proxy_pass this way or am I just doing something wrong?

Dynamic proxy_pass to $var with nginx 1.0

I was trying to use [Thin][1] app server and had one issue.

When nginx [proxies][2] the request to Thin (or Unicorn) using `proxy_pass http://my_app_upstream;` the application receives the modified URL sent by nginx (`http://my_app_upstream`). 

What I want is to pass the original URL and the original request from client with no modification as the app relies heavily on it.

The nginx&#39; [doc][2] says:

&gt; If it is necessary to transmit URI in
&gt; the unprocessed form then directive
&gt; proxy_pass should be used without URI
&gt; part.

But I don&#39;t understand how exactly to configure that as the related sample is actually using URI:


    location  /some/path/ {
      proxy_pass   http://127.0.0.1;
    }


So could you please help me figuring out how to **preserve the original request URL** from the client?


  [1]: http://code.macournoyer.com/thin/
  [2]: http://wiki.nginx.org/HttpProxyModule#proxy_pass

How to preserve request url with nginx proxy_pass

    upstream app_front_static {
        server 192.168.206.105:80;
    }

Never seen it before, anyone knows, what it means?

What does upstream mean in nginx?

How can I redirect `mydomain.com` and any subdomain `*.mydomain.com` to `www.adifferentdomain.com` using NGINX? 


How to redirect to a different domain using NGINX?

I&#39;m confused what purpose **[Mongrel2][1]** serves/provides that **[nginx][2]** doesn&#39;t already do.

*(Yes, I&#39;ve read the [manual][3] but I must to be too much of a noob to understand how it&#39;s fundamentally different than nginx)*

My current web application stack is: &lt;br&gt;
- **nginx**: webserver &lt;br&gt;
- **Lua**: programming language &lt;br&gt;
- **FastCGI + LuaJIT**: to connect nginx to Lua &lt;br&gt;
- **Postgres**: database


  [1]: http://mongrel2.org
  [2]: http://nginx.org
  [3]: http://mongrel2.org/static/mongrel2-manual.html

Why use Mongrel2?

How can I have same rule for two locations in NGINX config?

I have tried the following

    server {
      location /first/location/ | /second/location/ {
      ..
      ..
      }
    }

but nginx reload threw this error:

    nginx: [emerg] invalid number of arguments in &quot;location&quot; directive**

Content Type	Original Author	Original Content on Stackoverflow
Question	user650505	View Question on Stackoverflow
Solution 1 - Nginx	Martin Redmond	View Answer on Stackoverflow

Nginx location matches

Nginx Problem Overview

Nginx Solutions

Solution 1 - Nginx

How to start multiple processes in Bash

CONNECTIVITY_ACTION intent received twice when Wifi connected

Attributions