gmane.comp.web.nginx.english

Re: Rewriting

Francis Daly — 2013-05-25T10:07:15

Hi there,

You've got a few different things happening here, and I suspect that the
combination leads to you not getting the results you want.


So if I request "/file.php", this will rewrite to "/unav/file.php",
which probably doesn't exist, so I'm going to get a 404 unless you handle
it carefully.


The initial request was for "/". The explicit rewrite will make
that be "/unav/" (presuming that the rewrite applies here). In the
matching location{}, "/unav/" corresponds to a directory, not a file,
so there is an implicit rewrite to "/unav/index.html". This then
goes through the config again, and the explicit rewrite makes that
"/unav/unav/index.html". In the matching location{}, that does not
correspond to anything on the filesystem, hence 404.


What happens with that if my initial request is for "/dir/file.php"?



Back you your original issue:


So if I ask for "/dir/file.php" during this time, what response do you want
me to get?

The contents of one file? A redirection to a separate url? Something els

Re: Rewriting and proxy problem

Francis Daly — 2013-05-25T09:27:16

Hi there,


Welcome.

The nginx config follows its own logic, which may not match your previous
experiences. When you understand that, you'll have a much better chance
of knowing the configuration you are looking for.

One important feature is that one request is handled in one
location. Another is that one http request does not necessarily correspond
to one nginx request.

In this case...

you make the request for /demoX, and the best-match location is "location
/demo", and so that is the one that is used.


Once that happens, you are using the new internal-to-nginx request
"/upvc", so a new choice for best-match location happens, and the rest
of this location{} block is not relevant.



Aside: the fastcgi_params file will typically have content relevant for
when fastcgi_pass is used, not for when proxy_pass is used.

So, the http request for /demoX leads to the nginx request for /upvc,
which matches this location:


And here, you say "serve it from the filesystem", so that's what it does.

(I suspect that

Performance trouble after migration Squeeze to Wheezy

B.R. — 2013-05-24T21:16:03

Hello,

First of all I need to emphasize the fact that I know WHeezy is not yet
supported.
What I am trying to determine how WHeezy could impact Nginx (compiled for
Squeeze) performance.

Since I made the upgrade, big files are being served in a slow fashion
(~200 kiB/s).
The directory serving them is configured with AIO and worked perfectly
before system changes.

I know Sergey listed some changes in the
dependencies<http://mailman.nginx.org/mailman/listinfo/nginx>,
but what precisely would explain such a slow-down?
Is there a defect somewhere that I can work on or just be patient and wait
for the release of the Wheezy build of Nginx?

Thanks,
---
*B. R.*
_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg< at >public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx

Re: Rewriting and proxy problem

B.R. — 2013-05-24T19:06:00

Let's start by a huge RTFM?
http://nginx.org/en/docs/

This ML is no customer service for lazy people, I guess.
You may up for services to make other people do your job:
http://nginx.com/services.html

Best regards,
---
*B. R.*


On Fri, May 24, 2013 at 1:39 PM, Sergio Belkin <sebelk-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg< at >public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx

Rewriting and proxy problem

Sergio Belkin — 2013-05-24T17:39:58

H folks!

I am completeley newbie to nginx

I have the following config

        # Forward request to /demo to tomcat.  This is for
         # the BigBlueButton api demos.
       location /demo {
           rewrite ^ /upvc;
           proxy_pass         http://127.0.0.1:8080;
           proxy_redirect     default;
           proxy_set_header   X-Forwarded-For   $proxy_add_x_forwarded_for;

        # Allow 30M uploaded presentation document.
           client_max_body_size       30m;
           client_body_buffer_size    128k;

           proxy_connect_timeout      90;
           proxy_send_timeout         90;
           proxy_read_timeout         90;

           proxy_buffer_size          4k;
           proxy_buffers              4 32k;
           proxy_busy_buffers_size    64k;
           proxy_temp_file_write_size 64k;

           include    fastcgi_params;
       }


location /upvc {
        alias  /var/lib/tomcat6/webapps/demo;
        index demo3.jsp;
        expires 1m;
}


Rewrite is working but nginx

Re: Re[2]: Rewriting

B.R. — 2013-05-24T16:58:44

Pure wild guess:

Maybe a missing trailing slash in the request resulting in a temporary
redirection (and then processed again)?
Have you checked the requests made on the client side for any sign of
unwanted redirection? You could then use them to correct your rewrite
directive.

Hope I helped,
---
*B. R.*


On Fri, May 24, 2013 at 2:01 AM, wishmaster <artemrts-qsvJrrU2NvU< at >public.gmane.org> wrote:

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg< at >public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx

Re: proxy only certain assets based on host header?

Maxim Dounin — 2013-05-24T13:07:51

Hello!

On Thu, May 23, 2013 at 09:07:21PM -0400, amagad wrote:


Yes, sure.  Use separate server{} block for a domain name you want 
to be handled specially, e.g.:

     server {
         server_name foo.example.com;

         location / {
             # just serve anything as static
         }
     }

     server {
         server_name bar.example.com;

         location / {
             # server anything as static...
         }

         location /images/ {
             # ... but proxy images to a backend
             proxy_pass http://backend;
         }
     }

Re: valid_referers dynamic hostname

2013-05-24T11:10:47

Thanks alot! I made a logical error when writing your expression by thinking
that it will negate the comparison.

Also, I appreciate you have explained that http/https matching as I was
confused.


My best regards,
Vlad



Maxim Dounin Wrote:
-------------------------------------------------------

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239318,239507#msg-239507

Re: Override Content-Type header with proxied requests

andrea.mandolo — 2013-05-24T08:58:49

Thanks for the reply!!

This approach can be a good solution.
I wonder if this can affect the server perfomance.

Another solution could be to create a location for each file extension that
only adds the correct Content-Type header.
This is certainly less maintainable than a map, but is it better for the
perfomance ?

Does not exist any native Nginx directive (or in a third party module) that
permits Content-Type overriding (using Nginx mime.types "types" file) for
proxied requests ?

Thanks again!
---
Andrea

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239473,239502#msg-239502

Re: proxy only certain assets based on host header?

António P. P. Almeida — 2013-05-24T08:45:02

location ~ ^/(?:stylesheets|images|javascripts|tools|flash|components)/ {
     error_page 418 = < at >proxied_assets;

     if ($http_host = dnsname.com) {
         return 418;
     }

    # add other directives here if need be...
}

location < at >proxied-assets {
    proxy_pass http://assethost;
}


----appa



On Fri, May 24, 2013 at 3:07 AM, amagad <nginx-forum-LhBSS6c2AZM< at >public.gmane.org> wrote:

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg< at >public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx

Re[2]: Rewriting

wishmaster — 2013-05-24T06:01:58

Off course, you right. Thanks.

if ($remote_addr !~ '190\.212\.201\.[0-9]{0,3}') {
 rewrite ^/(.*)$ /unav/$1 break;
 }

location / {
 ....
 }
 ........

 But in log 

 2013/05/24 08:49:45 [error] 76017#0: *1910 open() "/usr/local/www/akbmaster/unav/unav/index.html" failed (2: No such file or directory), client: 190.212.201.198, server: akbmaster.server.com, request: "GET / HTTP/1.1", host: "akbmaster.server.com"

  I see twice rewriting.
  I have rewritten rule like this and this solved twice rewriting problem.
 rewrite ^/([^/]*)$ /unav/$1 break; 

 Can you explain me why in my situation nginx have rewritten request twice?

Cheers,

 

_______________________________________________
nginx mailing list
nginx< at >nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

[ANN] ngx_openresty devel version 1.2.8.5 released

agentzh — 2013-05-24T01:20:37

Hello guys!

I am happy to announce that the new development version of
ngx_openresty, 1.2.8.5, is now released:

    http://openresty.org/#Download

Special thanks go to all our contributors and users for helping make
this release happen!

Below is the complete change log for this release, as compared to the
last (devel) release, 1.2.8.3:

 *   upgraded LuaNginxModule to 0.8.2.

     *   feature: added "ngx.HTTP_MKCOL", "ngx.HTTP_COPY",
         "ngx.HTTP_MOVE", and other WebDAV request method constants;
         also added corresponding support to ngx.req.set_method and
         ngx.location.capture. thanks Adallom Roy for the patch.

     *   feature: allow injecting new user Lua APIs (and overriding
         existing Lua APIs) in the "ngx" table.

     *   bugfix: ngx.req.set_body_file() always enabled Direct I/O
         which caused the alert message "fcntl(O_DIRECT) ... Invalid
         argument" in error logs on file systems lacking the Direct
         I/O support. thanks Matthieu Tourne for reportin

proxy only certain assets based on host header?

amagad — 2013-05-24T01:07:21

We're trying to proxy only certain assets like png|jpg|css only when the
host header is a certain DNS name. I tried to do this in the proxy.conf file
using something the example below but it doesnt like the if statement. Is
there a way to have nginx do what I am looking for?


if ($http_host = dnsname.com) {
  location ~ ^/(stylesheets|images|javascripts|tools|flash|components)/ {
    proxy_pass http://assethost
  }
}

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239494,239494#msg-239494

Re: Rewriting

Bozhidara Marinchovska — 2013-05-23T21:47:15

Hello,

http://nginx.org/en/docs/http/request_processing.html

Because in this case you need to place your rule in server block if you 
would like to be valid for all custom defined locations in your config
For example:

server
{
listen 80;

if ($remote_addr ~ '192.168.1.25')
{
return 403;
}

location /
{
...
}

location ~ \.php$
{
...
}

}

On 23.05.2013 23:11 ч., wishmaster wrote:

_______________________________________________
nginx mailing list
nginx< at >nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Rewriting

wishmaster — 2013-05-23T20:11:49

Hi,
I use opencart with nginx+php-fpm. Sometimes it is necessary to redirect all clients, except admin (190.212.201.0/24), to "Service unavailable" page which is simple index.html file with logo, background image and some text, located in /unav directory.
Below  some of nginx.conf


location / {

if ($remote_addr !~ '190\.212\.201\.[0-9]{0,3}') {
rewrite ^/(.*)$ /unav/$1 break;
return 403;
}
try_files $uri $uri/ < at >opencart;
}

location ^~ /unav {
}

location < at >opencart {
rewrite ^/(.+)$ /index.php?_route_=$1 last;
}

[...skipped...]

location ~ \.php$ {

         try_files      $uri =404;
         fastcgi_read_timeout 60s;
         fastcgi_send_timeout 60s;
         include           myphp-fpm.conf;

                    }

Problem  is in rewriting.
This rule

rewrite ^/(.*)$ /unav/$1 break;

rewrite ONLY http://mysite.com/ request but in case http://mysite.com/index.php rewrite is none and request processed by location ~ \.php$ rule. Why??

Thanks!

Re: NGINX error log format documentation

Francis Daly — 2013-05-23T19:31:39

Hi there,

 
  less src/core/ngx_log.c

should probably show most of what you need. Combine that with

  grep -r -A 2 ngx_log_error src

and looking at an error log and you should see that it is "a small number
(five, I think) of fixed fields, followed by free-form text".


I (strongly) suspect that the error log line format details is not
something that nginx wants to commit to holding stable.

If you want to do any more parsing than "free-form text after a handful of
common fields", then you'll probably want to care about the version you
are using. Or at least, flag an imperfectly-recognised line if anything
doesn't match what you expect.


It's hard to beat the contents of src/ for accuracy.

Choose the "identifying" string in the line you care about, find the
matching ngx_error_log call, and then see what free-form text it provides
in the current version.

f

NGINX error log format documentation

Jan Teske — 2013-05-23T18:47:42

Hey!

I want to parse NGINX error logs. However, I did not find any 
documentation concerning the used log format. While the meaning of some 
fields like the data is pretty obvious, for some it is not at all. In 
addition, I cannot be sure that my parser is complete if I do not have a 
documentation of all the possible fields. Since it seems you can change 
the access log format, but not that of the error log, I really have no 
idea how to get the information I need.

Is there such documentation?

I also posted this question on StackOverflow: 
http://stackoverflow.com/questions/16711573/nginx-error-log-format-documentation/16711684

Thank you!


_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg< at >public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx

Re: streaming request

Pasi Kärkkäinen — 2013-05-23T18:13:11

People are asking for "no buffer" feature very often,
it's clearly something nginx is missing and should have. 

I know Weibin has been working on a patch to do exactly that ("no_buffer" patch).
Currently it's available and stable for nginx 1.2.x,
but the 1.4 version is still work-in-progress.

Re: Updated cross-reference (LXR)

artemg — 2013-05-23T15:43:40

If somebody wants cross reference for other versions, here you can find for
almost all versions on nginx http://osxr.org/ngx/source

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,220726,239479#msg-239479

Re: Override Content-Type header with proxied requests

António P. P. Almeida — 2013-05-23T15:33:41

Oops it's $upstream_http_content_type instead. Should read:

map $upstream_http_content_type $s3_content_type {
    # S3 -> real...
}


----appa



On Thu, May 23, 2013 at 5:24 PM, António P. P. Almeida <appa-rjfhcOcFV6XR7s880joybQ< at >public.gmane.org>wrote:

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg< at >public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx

Re: Override Content-Type header with proxied requests

António P. P. Almeida — 2013-05-23T15:24:07

Try this.

At the http level define a map directive that maps upstream Content-Types
to the correct ones.

map $upstream_content_type $s3_content_type {
    # S3 -> real...
}

On the location that proxy passes.

proxy_hide_header Content-Type;
add_header Content-Type $s3_content_type;

----appa



On Thu, May 23, 2013 at 5:07 PM, andrea.mandolo <nginx-forum-LhBSS6c2AZM< at >public.gmane.org>wrote:

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg< at >public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx