Use a resirect, keep it clean, simple, and compliant
Why waste reaources when you dont have to?
--
Payam Chychi
Network Engineer / Security Specialist
On Saturday, July 19, 2014 at 10:47 AM, Anoop Alias wrote:
>
>
>
> The Proxying server does not download the entire file ;save it to dis
The Proxying server does not download the entire file ;save it to disk and
then serve from that .
The proxy simply buffers the content (which is config manageable) and serve
the end user (browser ) .So the proxy will not face a high disk i/o load
like the origin ..
--
*Anoop P Alias*
GNUSYS
On Sat, Jul 19, 2014 at 5:57 PM, itpp2012 wrote:
> No :) I'd do it simple by using HTTP-EQUIV="REFRESH" as a response with an
> origin address.
>
Redirecting that way *might* work, although it looks a bit ugly to my
eyes. It also seems to be not compliant to WCAG if you care about
accessibilit
B.R. Wrote:
---
> > How? don't ask me :)
> >
>
> Is there a legal problem doing that? Why the smiley?
No :) I'd do it simple by using HTTP-EQUIV="REFRESH" as a response with an
origin address.
Posted at Nginx Forum:
http://forum.nginx.org/rea
On Sat, Jul 19, 2014 at 4:27 PM, itpp2012 wrote:
> shahzaib1232 Wrote:
> ---
> > Means, both server's i/o will be used if the requested file to
> > upstream is
> > 720p.mp4?
>
> Yes, what you're looking for is a way to client-rewrite the address
On Sat, Jul 19, 2014 at 11:51 PM, martyparish wrote:
> Unfortunately it did not. I was really hoping to do this with try_files
> instead of "if" and rewrite!
>
what error did you get
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailm
Unfortunately it did not. I was really hoping to do this with try_files
instead of "if" and rewrite!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251908,251941#msg-251941
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailm
On Sat, Jul 19, 2014 at 11:34 PM, martyparish wrote:
>
> actually this part was wrong;
> if (!-f $site_folder) {
> rewrite ^/[^/]+/(.*) /$1;
> }
>
> needs to be:
>
> if (!-d /etc/nginx/html/production/$site_folder) {
> rewrite ^/[^/]+/(.*) /$1;
> }
>
> * changed -f to -d
> ** had to add root path
actually this part was wrong;
if (!-f $site_folder) {
rewrite ^/[^/]+/(.*) /$1;
}
needs to be:
if (!-d /etc/nginx/html/production/$site_folder) {
rewrite ^/[^/]+/(.*) /$1;
}
* changed -f to -d
** had to add root path before $site_folder
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,
For anyone who comes across this scenario, here is how I got it working:
# get the first folder name into a variable ($site_folder)
map $uri $site_folder {
~^/(?P[a-zA-Z]+)/.*$folder ;
}
...
server {
...
shahzaib1232 Wrote:
---
> Means, both server's i/o will be used if the requested file to
> upstream is
> 720p.mp4?
Yes, what you're looking for is a way to client-rewrite the address the
source is coming from.
1.2.3.4 -> request xx.mp4 -> edge 5
Hi there,
function ngx_shmtx_lock:if (*mtx->lock == 0 &&
ngx_atomic_cmp_set(mtx->lock, 0, ngx_pid))
and ngx_trylock (ngx_atomic.h): (*(lock) == 0 &&
ngx_atomic_cmp_set(lock, 0, 1))
I think ngx_atomic_cmp_set is enough, why Nginx do extra judgement ahead of it ?
>>If nginx needs to proxy_pass, then before nginx sends content to client,
nginx asks upstream for content, and upstream sends content to nginx. So
the full file also goes from upstream to nginx.
Means, both server's i/o will be used if the requested file to upstream is
720p.mp4?
_
On Sat, Jul 19, 2014 at 02:23:49PM +0500, shahzaib shahzaib wrote:
Hi there,
> I am confused about the proxy_pass directive. Suppose, i need to serve an
> mp4 file from Origin server and using proxy_pass directive in Edge server,
> whose resources(I/o,bandwidth,Ram) will be used ? Edge or Origin
I am confused about the proxy_pass directive. Suppose, i need to serve an
mp4 file from Origin server and using proxy_pass directive in Edge server,
whose resources(I/o,bandwidth,Ram) will be used ? Edge or Origin ?
Following is the topology to server mp4 file :-
client (request mp4 file) --> edge
15 matches
Mail list logo