Re: 403 forbidden with lynx www browser

​Hello,​ On Mon, Nov 23, 2015 at 12:23 AM, Sylvain BERTRAND < sylvain.bertr...@gmail.com> wrote: > That's why I'm posting here: *Only nginx* www sites does block lynx. > Something > is not right there: a default aggressive blocking policy from nginx? > ​There is a difference between 'only

Re: 403 forbidden with lynx www browser

On Mon, Nov 23, 2015 at 10:23:20AM +1100, Sylvain BERTRAND wrote: > On Sun, Nov 22, 2015 at 05:25:11PM +, Francis Daly wrote: Hi there, > > Probably they have configured their servers to deny any request that > > includes "libwww" in the User-Agent. > > I'm about to block sending the user

Re: Complex url rewriting

Hello, You do not necessarily need to *redirect* *per se*, but you wish content to be served by your index.php files. Would location /index.php { location ~* (?:.*/index.php)(.*) { fastcgi_param SCRIPT_FILENAME $document_root$1; fastcgi_pass ; } } do the job? (untested)

Re: 403 forbidden with lynx www browser

You missed the parts where Francis and I suggested about testing against nginx.org and/or nginx.com websites. Is those reply correctly, the nginx product is definitely not the source of the trouble. I could also provide you with domains I serve with nginx, which do not use any sort of user-agent

[nginx] Configure: fixed using OpenSSL include paths.

details: http://hg.nginx.org/nginx/rev/520ec1917f1d branches: changeset: 6304:520ec1917f1d user: Maxim Dounin date: Mon Nov 23 22:48:31 2015 +0300 description: Configure: fixed using OpenSSL include paths. diffstat: auto/lib/openssl/conf | 1 + 1 files

RE: 403 forbidden with lynx www browser

B.R. Monday, November 23, 2015 2:26 PM On Mon, Nov 23, 2015 at 12:23 AM, Sylvain BERTRAND wrote: >>That's why I'm posting here: *Only nginx* www sites does block lynx. Something >>is not right there: a default aggressive blocking policy from nginx? >​There is a

Re: 400 Error on % !!

The '%' character has a meaning in the HTTP URI grammar, indicating that the following bytes are hexadecimal value representing a unicode character (see https://tools.ietf.org/html/rfc3986#section-2.1). If you try to implement what you suggest, you will basically corrupt URIs from someone tring to

Re: Complex url rewriting

Another note, on some of the application sub directories, I need to emulate this rule from .htaccess: RewriteRule ^(.*)$ %{DOCUMENT_ROOT}/index.php/$1 [QSA,L] Posted at Nginx Forum: https://forum.nginx.org/read.php?2,263024,263026#msg-263026 ___ nginx

Re: 400 Error on % !!

On Mon, Nov 23, 2015 at 08:34:41PM +0100, B.R. wrote: > On Mon, Nov 23, 2015 at 9:40 AM, shahzaib shahzaib > wrote: Hi there, [mostly addressed to the original poster] > > Thanks for the reply, now we've tons of these URLs which are not > > properly encoded. > The

Re: Complex url rewriting

Did you mean to use nested location blocks? I tried it but it didn't work. Here is the relevant part of my configuration file: # define web root root /var/www/html/public; index index.php index.html; location /index.php { location ~* (?:.*/index.php)(.*) {

400 Error on % !!

Hi, We've encountered with 400 Bad request error on nginx reverse proxy in front of apache. Here is the attached link : http://prntscr.com/95wlsl If we remove '%' from the URL, it works fine. What could be the issue ? Regards. Shahzaib Need to send me private email? I use Virtru

Re: 400 Error on % !!

On Mon, Nov 23, 2015, at 05:17 PM, shahzaib shahzaib wrote: > Hi, > >We've encountered with 400 Bad request error on nginx reverse proxy in > front of apache. Here is the attached link : > > http://prntscr.com/95wlsl > > If we remove '%' from the URL, it works fine. What could be the

Re: 400 Error on % !!

Hi, Thanks for the reply, now we've tons of these URLs which are not properly encoded. Can we redirect '%' request to the same URL by excluding '%' ? Such as http://domain.com/video/100%-working to http://domain.com/video/100-working Regards. Shahzaib On Mon, Nov 23, 2015 at 1:20 PM,

[ANN] OpenResty 1.9.3.2 released

Hi guys, I am glad to announce the new formal release, 1.9.3.2, of the OpenResty bundle: https://openresty.org/#Download The first highlight of this release is the new *_by_lua_block {} directives added in the ngx_http_lua module. For example, instead of writing content_by_lua '

Re: Unit testing approach for nginx modules

Hi Maxim, How these tests could be run? Do I need something special installed? On Mon, Nov 23, 2015 at 2:42 AM, Maxim Dounin wrote: > Hello! > > On Sat, Nov 21, 2015 at 09:40:57PM +, Ritesh Jha wrote: > > > Hello everyone, > > We are developing nginx modules to implement

Re: 403 forbidden with lynx www browser

On Mon, Nov 23, 2015 at 07:31:15PM +, Nelson, Erik - 2 wrote: > B.R. Monday, November 23, 2015 2:26 PM > On Mon, Nov 23, 2015 at 12:23 AM, Sylvain BERTRAND > wrote: > >>That's why I'm posting here: *Only nginx* www sites does block lynx. > >>Something > >>is not

Re: 403 forbidden with lynx www browser

*There is none so deaf than those who will not hear.* :o| ​Well​ if you two understand each other, find where nginx handles some user-agents differently than others. I am sure the developers would be more than glad to learn about it. Everyone is, actually. --- *B. R.* On Tue, Nov 24, 2015 at

Re: [PATCH] HTTP: implement 'connect' and 'close' phases

Hello! On Mon, Nov 23, 2015 at 03:05:07PM +, Alessandro Ghedini wrote: > On Fri, Nov 20, 2015 at 05:46:12pm +0300, Maxim Dounin wrote: > > Hello! > > Hi again, > > > On Fri, Nov 20, 2015 at 09:45:53AM +, Alessandro Ghedini wrote: > > > > > # HG changeset patch > > > # User Alessandro

Re: [PATCH] HTTP: implement 'connect' and 'close' phases

On Fri, Nov 20, 2015 at 05:46:12pm +0300, Maxim Dounin wrote: > Hello! Hi again, > On Fri, Nov 20, 2015 at 09:45:53AM +, Alessandro Ghedini wrote: > > > # HG changeset patch > > # User Alessandro Ghedini > > # Date 1447956026 0 > > # Thu Nov 19 18:00:26 2015

Re: bug of discarding request body

Hi, Maxim: Thank you very much for the comment, and sorry for my long previous email. I guess you might misunderstand my previous email. Basically what I try to say is that the *OLD* bug (ticket/669 as you mentioned) is seen on the *PRISTINE* *NEW* 1.9.7 release. The attached script

Complex url rewriting

I have a single Nginx installation and I am using PHP-FPM to serve multiple PHP applications in sub directories. Example: /var/www/ (this is 'root') /var/www/a/foo/index.php /var/www/a/bar/index.php /var/www/b/bar/index.php I want to setup url rewriting so that any request to

Re: bug of discarding request body

Hello! On Mon, Nov 23, 2015 at 09:26:46AM -0800, Shuxin Yang wrote: > Hi, Maxim: > > Thank you very much for the comment, and sorry for my long previous > email. > > I guess you might misunderstand my previous email. Basically what I try > to say > is that the *OLD* bug (ticket/669 as

Re: Поиск файла в двух папках

On Sunday 22 November 2015 17:38:20 Softer wrote: > Добрый день. Я делал в такой же ситуации вот так: > > location ~* > \.(cur|jpg|jpeg|gif|png|zip|tgz|gz|rar|bz2|jar|lzma|exe|pdf|ppt|tar|swf|ico|flv|mp3|doc|xls|wav|bmp|rtf|txt|xml|docx|xlsx|woff2?) > { > try_files $uri $uri/ @ph_static; >

Re: Complex url rewriting

Hi. Am 23-11-2015 18:48, schrieb lmauldinpe15: I have a single Nginx installation and I am using PHP-FPM to serve multiple PHP applications in sub directories. Example: /var/www/ (this is 'root') /var/www/a/foo/index.php /var/www/a/bar/index.php /var/www/b/bar/index.php I want to setup url

Re: bug of discarding request body

Hi, Maxim: Thank you so much for your insightful comment! Unbuffered-uploading not just to make things easier to reproduce the problem. It is trivial. So to speak. It is translating to say it is rather dangerous to use the unbuffered-uploading along with keepalive connections, as

[nginx] Core: enabled "include" inside http upstreams (ticket #6...

details: http://hg.nginx.org/nginx/rev/18428f775b2c branches: changeset: 6305:18428f775b2c user: Ruslan Ermilov date: Mon Nov 23 12:40:19 2015 +0300 description: Core: enabled "include" inside http upstreams (ticket #635). The directive already works inside stream