the config i am using is inherited from the designers of the elgg platform and i have explored it enough to know most of what it is doing. perhaps i need to replace the location block that targets .php files with one that explicitly lists all the possible locations of php files instead... which would leave the possibility open for the new 'stream' location block i am using here. i was using thby ura - Nginx Mailing List - English
ok, thanks. 1. i was thinking that this was the case, based on the results i have seen, yes. 2. ah, ok - i didn't appreciate that. i found this page with php code: http://licson.net/post/stream-videos-php/ is there a standard / recommended way to approach this with nginx? 3. i believe the problem i am encountering is that i am unable to explicitly redirect file requests for a specific pby ura - Nginx Mailing List - English
scenario: i am using a site built with the php based social framework called elgg (www.elgg.org) and am extending elgg to stream video. i discovered that nginx is not serving the mp4 files (for example) with the 'Accept-Ranges' header and thus without streaming support. i am searching for a way to remedy this. a 2nd issue is that the php overhead for repeatedly accessing the same file, throughby ura - Nginx Mailing List - English
one of the core elgg coders was speaking about using the X-Sendfile header to bypass php processing and serve the file directly, though i don't know enough about how the architecture of nginx/php would handle that to know if it would help here or not.by ura - Nginx Mailing List - English
after more exploration, i see that files which are placed in the root of my site can be preloaded and seeked correctly when played via the video.js package or directly as a video element. however, the videos that are played via the php application that runs my site are stored outside of the root directory of the site and i suspect that this is the cause of them not being streamed. (i am using theby ura - Nginx Mailing List - English
ok, thanks for clarifying. i just did a clean test as suggested and do indeed see the Accept-Ranges header being returned automatically by nginx. in doing that - the mp4 video still does not stream/pre-buffer as i am desiring. i accessed the test video file that is on the homepage of the video.js website via curl and there is no Accept-Ranges header being sent in the response for their fileby ura - Nginx Mailing List - English
i just did a test of inserting a meaningless header into the response, by adding the add_header directive into the various levels of the nginx config, beginning with http, then server and then the location that i have setup to focus on mp4 files. i found that the header is successfully inserted inside the http and server blocks, yet when i request an mp4 file via curl, the header is not returneby ura - Nginx Mailing List - English
this stackoverflow response on the topic is one that quotes the code i used... i have also seen this page linked by several other pages which said this was a workable approach: http://stackoverflow.com/questions/14598565/serving-206-byte-range-through-nginx-django i am not blindly following anything - i am looking at all the available information and referred to the nginx documentation - i amby ura - Nginx Mailing List - English
also.. since only the headers added via the final location block will be used, does this then mean that i need to put conditional logic into that block to check the current url for particular paths - if some headers are needed for some paths only.. ? since most of my served items will end in the .php location codeblock, if my thinking here is correct, i would essentially need to move nearly allby ura - Nginx Mailing List - English
thanks for responding here. the 206 code was advised by every tutorial i found online. i am using nginx 1.7.2, so cannot upgrade. >You shouldn't try to add Accept-Ranges header manually. It will >be added automatically when nginx supports range requests to the >resource in question. how do i notify nginx to serve particular file extensions with the accept-ranges header? whatby ura - Nginx Mailing List - English
i need to ensure the Accept-Ranges header is present to serve video files while supporting forward/backwards seeking. i notice in many tutorials for nginx that this header is shown as being present in server response headers by default, yet not on my present setup. i have used the following to add the header manually in the relevant places, yet so far have not been successful: # streamableby ura - Nginx Mailing List - English
i am creating a plugin for the elgg open source social networking framework, that adds the projekktor media player (http://www.projekktor.com/) to elgg. i am so far unable to get projekktor to seek video/audio files on the webserver (tested using nginx 1.5.13 + 1.7). i have asked on the projekktor forum and did not find a resolution there. essentially, i have the mp4 and flv add-ons activatedby ura - Nginx Mailing List - English
aha! yes, i needed to remove 'service'. now i see the correct 1.7 version code. thanks!by ura - Nginx Mailing List - English
those two commands don't show any version numbers, so i am not presently any closer to identifying the issue here. the paths returned look fine to me, from what i know already.by ura - Nginx Mailing List - English
thanks for assisting. i ran that command and see 3 repos which provide nginx. from what i see there, the 1.7.0-1 wheezy package is the candidate and also has been installed. i just checked my local development machine which is running lmde - the version of nginx is also the same spurious ubuntu 0.91 version.. yet the 2 machine are using different repos. i am not seeing 0.91 listed anywhere oby ura - Nginx Mailing List - English
after running the upgrade to 1.7.01 mainline version on debian, the nginx version check (service nginx -V) lists: 0.91-ubuntu1 - even though 1.7.01 is listed in the package manager in debian. does this mean that debains repos are serving an incorrect package?by ura - Nginx Mailing List - English
ah, oops.. i had forgotten to reload nginx on my development pc after changing the config.. so now the config doesn't work on both pcs! a step towards comprehension at least.by ura - How to...
i just found this site which has a converter for htaccess files - to create nginx files from them: http://winginx.com/htaccess i use the elgg framework (www.elgg.org) and i ran the htaccess file that comes with the elgg framework through this tool and the nginx config that was produced is running fine in my local development server - however, on my live server i am served a file for download inby ura - How to...
simple config issue here.. i am stuck though -> the location directive.. i want to deny access to the contents of a specific folder in a php app to only specific IPs. i read the nginx wiki and used: location /foldername/ { allow 127.0.0.1; ## drop rest of the world deny all; } thinking that this would result in only the named IP having access to the folder and it's contentsby ura - How to...
greetings all! i have been configuring a relatively low powered virtual server to serve a php app (a social network that is built using the elgg framework). i read this page (http://seravo.fi/2013/optimizing-web-server-performance-with-nginx-and-php) about optimising the nginx server and ran through the benchmarking process described there - tweaking various nginx options. i saw that my sitby ura - How to...
ah, i found the answer.. i needed to change the javascript mimetype to 'application/javascript'by ura - Nginx Mailing List - English
thanks for responding. :) so... has a change been made in the way i would activate the gzip process between the stable and mainline versions? in nginx.conf? this is the list of options i was successfully using in stable (built through trial and error): gzip on; gzip_http_version 1.0; gzip_comp_level 6; gzip_proxied any; gzip_min_length 100; gzip_buffers 16 8k;by ura - Nginx Mailing List - English
i just replaced a stable install with the mainline version (1.5.8) and noticed that the outputted files are not being gzipped. i ran nginx -V and do not see any arguments that enable gzip. is there a reason why the stable version included gzip and this mainline does not? do i need to manually build nginx to include the gzip module? if so, does that mean i need to rebuild nginx every time thereby ura - Nginx Mailing List - English