Show all posts by user
What you would like to see here at the site
What does the "event timer add" step in the debug log signify? - 7 years ago
am having a problem with trying to use oauth services in that the callback from the provider gets “stuck” on my server. The logs in the pastebin here: http://pastebin.com/qncJKVwQ summarise the experience. Nginx is setup as reverse proxy to Apache which handles PHP using CGI. that is, the old fashioned CGI and not fastCGI. So the stream of things see to be as follows: 1. Userby Dayo - Nginx Mailing List - English
Re: Switch off preview text - 13 years ago
Jim Thank you for finally removing the awful preview. I had stayed away for a few months as I found the site unusable due to this issue but coupled with your action on the notorious data eating issue, it looks like things are back on the up. Well done!by Dayo - Site Suggestions
Re: fastcgi_cache_bypass still not working? - 13 years ago
As there has been no new releases in the intervening period, I think the answer is obvious. As a work around, it may be possible to use 3rd modules like echo and proxy_purge to clear the cache before fulfilling the request whenever $nocache is set so that a fresh copy is cached afterwards. Never tried it before but looking at the docs, I'll think it should be within their range of capabilitiby Dayo - Nginx Mailing List - English
Re: Status 401 Behaviour Issue - 13 years ago
> Hi there, > > > I noticed a certain behaviour of the 401 status > code response I will like to change. > > > With Nginx however, if I define an html page > error_page for 401, this gets served every time a > user requests the protected directory and there is > no opportunity to fill in the authentication > details. > > That sounds odd to meby Dayo - Nginx Mailing List - English
Re: Status 401 Behaviour Issue - 13 years ago
> Do u mean a 403? No, 401 as written.by Dayo - Nginx Mailing List - English
Status 401 Behaviour Issue - 13 years ago
Hi all. I noticed a certain behaviour of the 401 status code response I will like to change. Firstly, in Apache, there is an html page for 401 that is defined in the error_page equivalent. When the request for a protected directory comes in, the user gets the form for the authentication and only if the authentication fails is that html page served. With Nginx however, if I define an htmlby Dayo - Nginx Mailing List - English
Re: Running nginx as reverse proxy with Apache, rewrite problem - 13 years ago
Try: Server { server_name site.com; listen 80; root /path/to/regular/content/; if ($http_user_agent ~* (mobile|android|blackberry|brew|htc|j2me|lg|midp|mot|netfront|nokia|obigo|openweb|opera\smini|palm|psp|samsung|sanyo|sch|sonyericsson|symbian|symbos|teleca|up.browser|wap|webos|windows\sce) ) { rewrite ^ http://mobile.site.com$request_uri redirect; } location /xyz/ { ... }by Dayo - Nginx Mailing List - English
Re: Problem with nginx/0.8.54 and alias - 13 years ago
Jim Nice to see that you seem to have resolved the data eating problem. I hope my post here: http://forum.nginx.org/read.php?6,30896 helped to locate the bit of code that needed changing. I hope you will also find the time to further improve the forum by adding the option to disable the preview for those that want this. Well done and keep up the good work!by Dayo - Nginx Mailing List - English
Re: what's the difference between "proxy_cache" and "fastcgi_cache"? - 13 years ago
pig Wrote: ------------------------------------------------------- > I know that "proxy_cache" is often used for static > pages(or elements), and "fastcgi_cache" is usually > used for dynamic script(*.php,*.jsp etc.). > > But what's difference between their > implementation? what content is cached by > "fastcgi_cache", the scripby Dayo - Nginx Mailing List - English
Re: nginx.conf questions - 13 years ago
Just skip the "server_name example.com;" bit. You don't need the rewrite server for IP address based server. server { listen 80; root /path/to/your/document/root/; access_log /path/to/where/you/want/to/keep/your/access.log; error_log //path/to/where/you/want/to/keep/your/error.log; location /example/ { index index.html; .... } location / { index index.html; .... }by Dayo - Nginx Mailing List - English
BB Code and HTML Stripping Issues - 13 years ago
Hi Jim. Moving on from the testy exchanges, I downloaded a copy of Phorum and had a look at the source to try to figure out what was causing the issues and I have some code that I think should resolve them. Basically, the problem is in two lines of "function phorum_strip_body" of "/include/format_functions.php" which while they say "Strip HTML <tags>" andby Dayo - Site Suggestions
Re: Passing variables to access_log, error_log names - 13 years ago
Jim Ohlstein Wrote: ------------------------------------------------------- > -- > Jim Ohlstein > On Feb 27, 2011 11:28 AM, "Dayo" wrote: > > > > Maxim Dounin Wrote: > > > -------------------------------------------------- > ----- > > > > server { > > > > listen 80; > > > > server_name > ~^(www\.)?(by Dayo - Nginx Mailing List - English
Re: Passing variables to access_log, error_log names - 13 years ago
Maxim Dounin Wrote: ------------------------------------------------------- > > server { > > listen 80; > > server_name ~^(www\.)?(?P[^.]+).mydomain.com$; > > Just a side note: forum is still eating data > (originally > "P" was here), you may want to consider using > mailing > list directly instead. Unfortunately, the mailing list iby Dayo - Nginx Mailing List - English
Re: Switch off preview text - 13 years ago
Hi Jim. Knowing how busy you are and bearing I mind your post elsewhere asking for coding assistance, I wonder what I can do to assist you with implementing an option to disable the preview text for those that want it disabled. Cheers.by Dayo - Site Suggestions
Re: Problem with nginx/0.8.54 and alias - 13 years ago
Jim Ohlstein Wrote: ------------------------------------------------------- > I addressed your issue about which you haven't > made "multiple" > complaints. It seems that you are the *only* one > complaining about it > despite there being nearly 4000 registered users. > See above. > > > I host and administer the forum in the little > spare timby Dayo - Nginx Mailing List - English
Re: Problem with nginx/0.8.54 and alias - 13 years ago
Здравствуйте! Maxim Dounin Wrote: ------------------------------------------------------- > > > Just a side note: forum is awful, it eats > data. > > > > To be fair to the forum, I was the one that > truncated the quote to only > > show the relevant part to my post. > > The long and complex quotes become impossible > for me to follby Dayo - Nginx Mailing List - English
Re: Alias causing phpMyAdmin login endless loop - 13 years ago
"location ~ ^/phpmyadmin/(.*\.php)$" -->> How about all the other phpMyAdmin files that are not .php files? This works for me (Replace 'proxy' with 'fastcgi'). server { location ~ .+\.php$ { # Return '400 Bad Request' for dodgy urls; location ~ \..*/.*\.php$ { return 400; } # Send others to proxy; error_page 402 = @proxy; return 402; } location ~by Dayo - Nginx Mailing List - English
Re: Problem with nginx/0.8.54 and alias - 13 years ago
Hi Maxim! Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > > On Thu, Feb 17, 2011 at 01:09:15PM -0500, Dayo > wrote: > > > Igor Sysoev Wrote: > > > -------------------------------------------------- > > > Use late 0.8.x with this configuration: > > > > > > location ~ ^/phpmyadmin/(?.+\by Dayo - Nginx Mailing List - English
Re: Problem with nginx/0.8.54 and alias - 13 years ago
Igor Sysoev Wrote: ------------------------------------------------------- > Use late 0.8.x with this configuration: > > location ~ ^/phpmyadmin/(?.+\.php)$ { > fastcgi_pass 127.0.0.1:9000; > fastcgi_param SCRIPT_FILENAME > > /var/www/monsite.fr/phpMyAdmin/$NAME; > include fastcgi_params; > } Tried this out on 0.8.54 and goby Dayo - Nginx Mailing List - English
Re: remove www from the url - 13 years ago
Jim Ohlstein Wrote: > Not to be *too* pedantic, but unless you are using > both http and https, > using $scheme is unnecessary. I only use it for > such situations. Without > having read the code (not that I'd likely > understand it anyway), and > Igor can comment on this, it would seem a waste. A bit too pedantic I think as you will note that the examples do not inby Dayo - Nginx Mailing List - English
Re: Choose upstream based in a cookie - 13 years ago
I don't know if that will work (see http://wiki.nginx.org/IfIsEvil) This will almost certainly work: location / { set_by_lua $backend_ip ' if ngx.var.cookie_memberid ~= "" and ngx.var.cookie_memberid ~= nil then return "10.10.10.10" elseif ngx.var.cookie_clientid ~= "" and ngx.var.cookie_clientid ~= nil then return "10.10.10.15"by Dayo - Nginx Mailing List - English
Re: remove www from the url - 13 years ago
edogawaconan Wrote: ------------------------------------------------------- > If I remember correctly: > > server { > server_name www.mysite.com; > rewrite ^ $schema://mysite.com$request_uri > permanent; > } Good memory. Not "$schema" though, but "$scheme" server { server_name www.mysite.com; rewrite ^ $scheme://mysite.com$request_uby Dayo - Nginx Mailing List - English
Re: How nginx's "location if" works (Was Re: Setting cache parameters via if directives) - 13 years ago
Ryan Malayter Wrote: ------------------------------------------------------- > So what is a generally safe way to handle control > flow where the > conditions are based on something that is not in > the URI (making > rewrite useless)? Have a look at this: http://forum.nginx.org/read.php?2,161969,167787#msg-167787 May be usefulby Dayo - Nginx Mailing List - English
Re: How nginx's "location if" works (Was Re: Setting cache parameters via if directives) - 13 years ago
Ryan Malayter Wrote: ------------------------------------------------------- > I guess this sort of thing could always be a job > for a general-purpose > web server like Apache. Nginx is meant to be > simple and lightweight; > perhaps the general design is at odds with complex > flow control. On the contrary, it seems to me that one cannot even begin to contemplate theby Dayo - Nginx Mailing List - English
Re: Memcache and garbled text returned by Nginx - 13 years ago
Jim Ohlstein Wrote: ------------------------------------------------------- > > http://konstruktors.com/ everything is OK, while > this > > http://konstruktors.com/blog/ returns the > garbled string. > > This page renders normally in current Mac versions > of Firefox, Opera, > and Safari for me. No problem viewing the page either here as well.by Dayo - Nginx Mailing List - English
Re: Passing request directly to named location - 13 years ago
Dayo Wrote: ------------------------------------------------------- > That is the great thing about this little > webserver you have written ... it allows tons of > options and with agentzh and the other fellas in > Shanghai coming out with all sorts of crazy > modules, it is just mouth watering. > > Would be nice if some of the stuff coming out of > Shanghai coulby Dayo - Nginx Mailing List - English
Re: Nested Locations Better??? - 13 years ago
Igor Sysoev Wrote: ------------------------------------------------------- > > How about the other way round? Non regex nested > in regex? > > > > location ~ set { > > location /subset/ { > > ... > > } > > } > > > > Not likely to be common but possible. Any views? > > You may use it, buby Dayo - Nginx Mailing List - English
Re: Nested Locations Better??? - 13 years ago
Hi Igor. Igor Sysoev Wrote: ------------------------------------------------------- > The nested locations are better if you > had to use regex > locations. Then I usually isolate regex location > inside usual location: > > location /dir/ { > location ~ ^/dir/(.+)$ { > ... > } > } How about the other way round? Non regeby Dayo - Nginx Mailing List - English
Re: Nested Locations Better??? - 13 years ago
Igor Sysoev Wrote: ------------------------------------------------------- > If you use only locations without regexes, then > you may not use nested > locations. nginx uses some kind of binary tree to > match locations, so > > location /set/subset/ { } > location /set/ { } > > are slightly faster than nested locations. BTW you > may write > >by Dayo - Nginx Mailing List - English
Nested Locations Better??? - 13 years ago
Just noticed that in Igor's response to an earlier query of mine on a separate issue, he took code I had shown effectively as ... location /set/subset/ { abc; } location /set/ { xyz; } ... and wrote it like this in his response ... location /set/ { location /set/subset/ { abc; } xyz; } I had put the first location block on top so that it would be processed sinceby Dayo - Nginx Mailing List - English
 |
 |
 |
 |
|