Ah, votre problème semble être un peu compliqué, je ne pourrais pas vous
aider, désolé
--
Posted via http://www.ruby-forum.com/.
___
nginx mailing list
nginx@nginx.org
http://mailman.ng
Hello!
On Fri, Jul 04, 2014 at 09:48:04AM -0400, ura wrote:
> 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 explici
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 wou
Hello!
On Mon, Jun 30, 2014 at 04:34:51PM -0400, ura wrote:
> 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 st
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 proble
Hello!
On Sat, Jun 28, 2014 at 11:25:30AM -0400, ura wrote:
> 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 t
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.
Posted at Nginx Forum:
http://forum.nginx.org
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 di
Hello!
On Fri, Jun 27, 2014 at 07:26:04PM -0400, ura wrote:
> 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
> desirin
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
Hello!
On Fri, Jun 27, 2014 at 02:23:47PM -0400, ura wrote:
> 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-
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 in
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 anythi
Hello!
On Fri, Jun 27, 2014 at 12:54:09PM -0400, ura wrote:
> 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.
Ok, so your problem is likely due to "return 206" added. Just
remove it, as well as other garbage
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 .
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 noti
Hello!
On Fri, Jun 27, 2014 at 11:50:47AM -0400, ura wrote:
> 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 d
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
18 matches
Mail list logo