i get these in PHP just fine, it seems to work okay. $_SERVER['HTTP_CONTENT_RANGE'] $_SERVER['HTTP_CONTENT_DISPOSITION'] On Thu, Jul 23, 2009 at 9:50 AM, Magdalena<theglobeisnowdigital@gmail.com> wrote: > Has anyone used the fastcgi to get the "range" header field from the http? I > believe there is a bug associated with it. >by mike - Nginx Mailing List - English
most likely igor would say separate server {} blocks On Wed, Jul 22, 2009 at 6:05 PM, vburshteyn<nginx-forum@nginx.us> wrote: > so what should i use? > > Posted at Nginx Forum: http://forum.nginx.org/read.php?2,4346,4349#msg-4349 > > >by mike - Nginx Mailing List - English
location doesn't work on hosts, only on paths/etc. On Wed, Jul 22, 2009 at 5:26 PM, vburshteyn<nginx-forum@nginx.us> wrote: > hey folks, i got a quick question > > basically my issue is this. the main site is mysite.com > > so > > location / { works great > > but then i have a.mysite.com/boxoffice > > when there is /boxoffice the A variablby mike - Nginx Mailing List - English
http://php-fpm.org/downloads/freebsd-port/php-5.2.10-fpm-0.5.13.tar.gzby mike - Php-fpm Mailing List - English
Thank you sir - I'm waiting to hear back from Andrei if he's cool with me dumping his last iteration of code out to the public. I've started a launchpad project for it, but since he did some new code I just want to run it by him quick. I don't know if he has some more code he'd like to throw out there first or not. Launchpad will make it easy to collect bugs, feature requests, developer coby mike - Php-fpm Mailing List - English
thttpd, apache ... On Tue, Jul 21, 2009 at 4:39 PM, Ian M. Evans<ianevans@digitalhit.com> wrote: > I have just a couple of small cgi programs that I use for some mail admin > functions. Barely ever use them. > > Is there a small footprint web server that could handle just those pages? I > guess I'd put it behind nginx so nginx could handle the SSL. > >by mike - Nginx Mailing List - English
or fcgiwrap On Tue, Jul 21, 2009 at 4:39 PM, Ian M. Evans<ianevans@digitalhit.com> wrote: > I have just a couple of small cgi programs that I use for some mail admin > functions. Barely ever use them. > > Is there a small footprint web server that could handle just those pages? I > guess I'd put it behind nginx so nginx could handle the SSL. > >by mike - Nginx Mailing List - English
The text is being truncated on very long files/dirs - and it does not appear there is any option to make it longer or just be the entire length. Seems like a pretty simple change. I think Apache handles it properly - just let the browser wordwrap them... For example: http://runtests.syncevolution.org/2009-07-18-16-54/head-evolution-testing/11-zyb/by mike - Nginx Mailing List - English
2009/7/21 Igor Sysoev <is@rambler-co.ru>: > http { > > # here you may set any fastcgi settings expect fastcgi_pass, > # and they will be inherited in all servers and locations. > fastcgi_index ... > fastcgi_param ... The only negative about this is (how Maxim described it) any "array" type configuration item like fastcgi_parby mike - Nginx Mailing List - English
On Mon, Jul 20, 2009 at 4:52 PM, Marcus Clyne<maccaday@gmail.com> wrote: > Wrt PHP, I've not tried it out so I'm not sure precisely how it works. I'm > assuming that all directories are searched, though, and that lower-levels > override higher levels. In that case, it makes sense to start at the > bottom, since then you will only set each option once - if you discover tby mike - Nginx Mailing List - English
that too! didn't even think about that, duh :) i think having a limited htaccess support module would be great, and for the most part, i think servers can handle a few extra stat calls cached appropriately (doesn't the filesystem have caching type things, or inotify/dnotify/kernel notifications, etc) scaling that is probably a lot easier especially if it can be turned on/off by locationby mike - Nginx Mailing List - English
On Mon, Jul 20, 2009 at 3:22 PM, Kaspars<kaspars@konstruktors.com> wrote: > I agree. My suggestion was to allow only one config file per host in a > defined location instead of unlimited amount of config files in all possible > locations. that is another way to look into it. a site-wide .htaccess. however, if multiple people are collaborating on a single site and some peoplby mike - Nginx Mailing List - English
On Mon, Jul 20, 2009 at 3:13 PM, Marcus Clyne<maccaday@gmail.com> wrote: > That would be overall less efficient, since if you had htaccess-like files, > you would always want to check the uppermost level (because it might say to > ignore htaccess files lower down). If it did, then you will have checked > lower-level htaccess files unnecessarily. I'm not sure; I think iby mike - Nginx Mailing List - English
that would require server level configuration still... the idea is to give the users a way to configure things on their own. On Mon, Jul 20, 2009 at 2:25 PM, Kaspars<kaspars@konstruktors.com> wrote: >> >> http://foo.com/1/2/3/ >> >> would chekc for >> >> /home/foo/bar/foo.com/1/2/3/ >> /home/foo/bar/foo.com/1/2/ >> /home/foo/bar/fooby mike - Nginx Mailing List - English
i agree. i think there should be an htaccess on; type deal, and instead of going / /home /home/foo /home/foo/bar /home/foo/bar/foo.com in the search path, it should start in the document root. in php 5.3, they actually take the file path being requested, and then go backwards from there, down to the document root level. so http://foo.com/1/2/3/ would chekc for /home/foo/barby mike - Nginx Mailing List - English
Igor, right now any time you have to protect a location, you have to put in a second location block for php. You've said yourself this isn't a highly suggested method. I've also run into issues where my expires headers can sometimes conflict with things... would there be some way to implement some sort of global location block method? perhaps it gets applied -after- the normal locationby mike - Nginx Mailing List - English
oops, misread SCRIPT_NAME as SCRIPT_FILENAME just for giggles try this instead location ~ \.php$ { On Sat, Jul 18, 2009 at 12:19 PM, Glen Lumanau<glen@lumanau.web.id> wrote: > It's already set > > Here's the config > location ~ .php$ { > fastcgi_pass 127.0.0.1:9000; > fastcgi_index index.php; > fasby mike - Nginx Mailing List - English
Change the script_filename one to $document_root$fastcgi_script_name Sent from my iPhone On Jul 18, 2009, at 9:33 AM, "Glen Lumanau" <glen@lumanau.web.id> wrote: > Here's my default fastcgi_params > > fastcgi_param QUERY_STRING $query_string; > fastcgi_param REQUEST_METHOD $request_method; > fastcgi_param CONTENT_TYPE $content_tby mike - Nginx Mailing List - English
no clue, but it sounds like it changes how the script_filename is done. perhaps turn on debug on nginx, and see what SCRIPT_FILENAME says (it should still be the same) but due to the basedir you might need to take out $document_root and only put in $script_name (perhaps open_basedir is essentially chrooting things?) On Thu, Jul 16, 2009 at 12:40 PM, Neves<marcos.neves@gmail.com> wby mike - Php-fpm Mailing List - English
Sure. Well it's good to know it's not localized to fpm. I'm thinking when you do that the script filename changes, and you may have to alter the fastcgi_param in nginx... On Thu, Jul 16, 2009 at 11:54 AM, Neves<marcos.neves@gmail.com> wrote: > > I´ve tried with spawn-fcgi too, and the same problem happens. > I just want to share this with you. > > On 16 jul, 14:by mike - Php-fpm Mailing List - English
Is there a way you can test a normal non-FPM version with this? I don't believe the FPM patchwork should change this behavior (of course, I've been wrong many times) On Thu, Jul 16, 2009 at 4:43 AM, Neves<marcos.neves@gmail.com> wrote: > > One feature of php 5.3 that I was waiting for is this one from > php.ini: > > > max_execution_time=1 > memory_limit=8Mby mike - Php-fpm Mailing List - English
On Thu, Jul 16, 2009 at 5:41 AM, Maxim Dounin<mdounin@mdounin.ru> wrote: > See no reasons to test $uri twice. I think it's a typo. probably meant try_files $uri $uri/ /index.php;by mike - Nginx Mailing List - English
post your configuration On Thu, Jul 16, 2009 at 2:27 AM, gerryw<nginx-forum@nginx.us> wrote: > Hello All, > > I also did a test with just the vanilla FastCGI API calls. The only env related variable I was able to get was "REQUEST_METHOD". None of the rest were set. > > Thanks, > Gerry > > Posted at Nginx Forum: http://forum.nginx.org/read.php?2,40by mike - Nginx Mailing List - English
what webserver are you using, just for kicks? On Thu, Jul 16, 2009 at 4:43 AM, Neves<marcos.neves@gmail.com> wrote: > > One feature of php 5.3 that I was waiting for is this one from > php.ini: > > > max_execution_time=1 > memory_limit=8MB > open_basedir=/var/www/my.domain.com > doc_root=/var/www/my.domain.com > > > Every thing works fine,by mike - Php-fpm Mailing List - English
Wed, Jul 15, 2009 at 10:53 PM, Jim Ohlstein<nginx-forum@nginx.us> wrote: > This is an unprofessional way to handle this. The problem is, in this case, that ./configure works fine without the "--enable-fastcgi" option but then compilation fails and it's not immediately obvious as to why that is. Those of us who actually read the documentation *know* that "--enable-fastcgiby mike - Php-fpm Mailing List - English
well yes, it is nit picking - of course, if you give it the other fpm options at configure time those are invalid too... so just configure --enable-fastcgi a requisite for compilation of php-fpm :) there -is- a standalone version of (php-)fpm in the works. it still requires compilation against php sources, but it does not alter php and is no longer a patch. means a lot easier to distributeby mike - Php-fpm Mailing List - English
ideally it would be listen 1.2.3.4:443 default ssl; right? otherwise this block will be the default ssl host for anything else unmatched. i typically use ip:443 in all my ssl stuff to ensure i am only going to serve up the cert on the proper sites anyway. On Tue, Jul 14, 2009 at 1:16 PM, Maxim Dounin<mdounin@mdounin.ru> wrote: > Hello! > > On Tue, Jul 14, 2009 at 04:06:by mike - Nginx Mailing List - English
http://marc.info/?l=nginx&m=124747329127204&w=2 http://marc.info/?l=nginx&m=124747239025852&w=2 http://marc.info/?l=nginx&m=124747216625615&w=2 On Tue, Jul 14, 2009 at 1:06 PM, Ilan Berkner<iberkner@gmail.com> wrote: > If you can point it out to me... I searched, can't find it. > > On Tue, Jul 14, 2009 at 3:58 PM, Michael Shadle <mike503@gmail.com&by mike - Nginx Mailing List - English
someone just posted a config example in the past couple days about this On Tue, Jul 14, 2009 at 11:14 AM, Ilan Berkner<iberkner@gmail.com> wrote: > >by mike - Nginx Mailing List - English
We've actually already began work and such and there has been a conference call between andrei and some of the php folks who manage the fastcgi sapi. It is in no way dead but it may be changing course slightly, this course however will make it easier to contribute (anyone) and won't require parching php anymore. Sent from my iPhone On Jul 13, 2009, at 7:42 PM, Floren Munteanuby mike - Php-fpm Mailing List - English
![]() |
![]() |
![]() |
![]() |
|